Slashdot Mirror
DOOM 3DO Source Released On Github
New submitter burgerbecky writes The port that was as hellish as the game world itself, DOOM for the 3DO's source code has been released on github. The original programmer outlined the corners cut and why.
← Back to Stories (view on slashdot.org)
It's interesting just to look at the overall organization of the code, although relatively few will probably invest hours in getting to know it well.
I noticed that the source code is released under the MIT license, but the submitter/coder also points out the DOOM 3DO IP is owned by ZeniMax, who retains exclusive rights. I assume that applies to names, trademarks, and graphics only.
http://youfailit.net/?p=49
My guess is this guy will start selling this game, claiming he programmed it, and a 3DO emulator source he'll also claim as he did.
Be seeing you...
I had some opportunity to work with HP-UX (built GnuMake on it for a in-company build/QA system), it was always an interesting and very different beast. Is it still around in any form?
Yes.
Another over-simplified common argument from someone that doesn't know anything about unions, just knows that they don't like them, because, uh... Ayn Rand! or something.
Steelworker jobs disappeared as a result of automation. One quick example that you can find in 5 seconds of googling:
“When I joined the company, it had 28,000 employees,” said George Ranney, a former executive at Inland Steel, an Indiana mill that was bought out by ArcelorMittal in 1998. “When I left, it had between 5,000 and 6,000. We were making the same amount of steel, 5 million tons a year, with higher quality and lower cost.”
But keep spreading that myth of "unions=job loss". They're lapping it up in the red states. Amazing how so many middle-class people will vote against their own self-interests.
I've learned that they're worthless, so I don't read AC comments anymore.
You're correct - http://en.wikipedia.org/wiki/R...
S/he was born William Salvador Heineman
Pain is merely failure leaving the body
The ARM linker for the 3DO will link each and every function in the source file if only one function in a file was used. It was common practice in the 80s and 90s to write library code with each function in its own source file to get around the problem of accidental code bloat. Look to the early GNU stdlib implementation and you'll notice they did the same thing. Modern linkers with Link Time Code Generation don't suffer from this issue since they will remove every piece of dead or unused code wherever it is, which is why Burgerlib 5 is in a lot fewer source files than Burgerlib 1, 2 or 3.
The code's very readable - bonus points for style.
Seriously? It has a DO loop inside of a GOTO loop inside of another GOTO loop. Those are the ones I've found so far. Also, it doesn't actually abort when it goes to ABORT.....from there it jumps back to AGAIN. The structure of that code is exactly why GOTOs are considered evil.
And for the record, I don't oppose gotos, but I do oppose them used in ugly code.
"First they came for the slanderers and i said nothing."
And if anybody doesn't understand: The goto statement is considered harmful, except when it's not. When used in situations where structured programming (while and friends) expresses the intent more cleanly, it's harmful. But when used as the backend of a coroutine macro library, it's not. And when used to jump to cleanup code in exceptional conditions, as seen here, it's not.
Would you prefer they continue to suffer without offering resistance then? Do you believe they had some readily available option which they refusedf to use? That is a bit hard to say from the perspective of people over a century later.
You could ask Thomas Jefferson, Abraham Lincoln, even Moses, their thoughts as well.
Well let's have a look at the times before modern labor unions:
In the eighteenth century something approximating permanent labor organizations or trade unions were beginning to emerge from the industrialization of Great Britain. But in colonial America, as a general rule, the laborer procured the terms desired without having to combine with others. When American workers did take concerted action, it was invariably for a specific grievance and did not result in a permanent organization. The cases where master carpenters set up price scales for their trade are the exception. In certain trades, master workers combined to secure or maintain a monopoly of business operations and to prevent others from entering their trades, but such restraints were rapidly diminishing as the eighteenth century advanced. In the licensed trades, those who acted in concert were generally the employers. They combined with others in the same trade to secure better fees or prices, which were customarily regulated by local authority for the public interest. Today such combinations would be subject to antitrust laws.
http://www.dol.gov/dol/aboutdo...
Which by the way, this also explains why trade unions were VERY unpopular during the early years of America. Ben Franklin in particular was outspoken against them.
"burgerbecky" is Rebecca Heineman, who programmed The Bard's Tale III and Dragon Wars, two of my favorite old computer RPG's. I had no idea she worked on 3DO Doom.