Main > Everything Else

Spammin' the boards!

<< < (7/9) > >>

SavannahLion:
So what is the complaint? The bloat?

Ed_McCarron:

--- Quote from: SavannahLion on February 05, 2011, 09:57:53 pm ---So what is the complaint? The bloat?

--- End quote ---

Well, y'know, with 640k of RAM and a 20M hard drive, one has to be careful what one keeps on their computer.

Oh, no, wait, this isn't 1991.  I'm not sure what the complaint is.

BadMouth:

--- Quote from: SavannahLion on February 05, 2011, 09:57:53 pm ---So what is the complaint? The bloat?

--- End quote ---

The binary Derrick uploaded was 2mb bigger because it wasn't compiled the same way as the standard mame binary.
Therefore Abaraba has concluded that Derrick's code resulted in 2mb of bloat (even though it's only a couple dozen lines of code).

Abaraba's code, which he created by following the step by step instructions found here:
http://www.jstookey.com/arcade/720/720-arcadejoy.php
is done in less lines of code, but it does not handle the calibration disc the way the original game did.

Wanting the driver to reflect the way the original equipment handled the input was what started this whole 720 debacle.

MonMotha:

--- Quote from: pinballjim on February 06, 2011, 11:56:21 am ---
--- Quote from: BadMouth on February 06, 2011, 10:06:44 am ---The binary Derrick uploaded was 2mb bigger because it wasn't compiled the same way as the standard mame binary.
Therefore Abaraba has concluded that Derrick's code resulted in 2mb of bloat (even though it's only a couple dozen lines of code).

--- End quote ---

lol wut

 :laugh2:

--- End quote ---

This is actually quite common.

Compiler and linker (especially) options can have quite an effect on the output size.  For example, if the original binary is dynamically linked while the new one is statically linked, an additional 2MB is reasonable and possibly even on the small side.  Changing compiler optimization flags can do something similar, though the effect isn't usually as huge as some of the linker options.  Heck, sometimes just using a different VERSION of the same compiler (let alone if you're using a different compiler) with the same options can change the size of the output by a fair margin. 

Inclusion/exclusion of debugging symbols can also be pretty dramatic, especially on a diverse application like MAME.  These debugging symbols don't actually do anything when running the program, but if they're present, it's a lot easier to debug the program with a debugger or via crash reports.  Including such things seems perfectly reasonable for an experimental build, but the normally distributed version of MAME probably doesn't have them.

Besides, who cares about 2MB at this point?  It'll take me another 5 seconds to download (on a 4-5Mbps connection) and use another 0.0002% of my hard drive (1TB hard drive).  Oh noes!  If it's truly unnecessary bloat, then, sure, look to get rid of it, but on a test build to check out a concept, it's not a big deal.  It's not someone added 2GB to the thing.

DillonFoulds:

--- Quote from: saint on February 05, 2011, 06:16:01 pm ---
--- Quote from: wp34 on February 05, 2011, 05:14:05 pm ---
--- Quote from: fernandez on February 05, 2011, 03:56:37 pm ---Oh, by the way... as a token of friendship and good will, I will not spam the forum with this 'clone' of mine. -- In return, I ask the source code, and possibly binary too, of Derrick's NEW changes is made available to public, BUT separate from the rest of 141u1 changes.

--- End quote ---

This is like a bad movie.  Does Saint negotiate with terrorists?

--- End quote ---

No.

--- End quote ---

I wonder if saint can change usernames for banned accounts? I mean, just have a bit of fun with it... Driver-Ban, Ferbandez, etc. etc.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version