 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New <dne### [at] san rrcom> wrote:
> > You had a C compiler in a machine with 8k of memory? Which one was that?
> PDP-11? I had a machine with a COBOL compiler that ran in 8K of
> real-live core memory. And, like, it ran banks and stuff. :-)
An entire C or COBOL compiler which can run and compile with only
8 kilobytes of memory puts those 4k intros into shame, IMO. :P
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> An entire C or COBOL compiler which can run and compile with only
> 8 kilobytes of memory puts those 4k intros into shame, IMO. :P
What's a 4k intro?
(Of course, it had lots of passes. And a 50-line program took maybe 10
or 15 minutes to compile. But there was no VM either, for what that's
worth to the discussion. :-)
--
Darren New / San Diego, CA, USA (PST)
Helpful housekeeping hints:
Check your feather pillows for holes
before putting them in the washing machine.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New <dne### [at] sanrrcom> wrote:
> Warp wrote:
> > An entire C or COBOL compiler which can run and compile with only
> > 8 kilobytes of memory puts those 4k intros into shame, IMO. :P
> What's a 4k intro?
http://en.wikipedia.org/wiki/Demo_(computer_programming)#Intros
It's rather incredible what you can squeeze into that amount of bytes.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> http://en.wikipedia.org/wiki/Demo_(computer_programming)#Intros
>
> It's rather incredible what you can squeeze into that amount of bytes.
Yarr, back then, coders were *real* coders! Haharrr!
Mmm, can't see me entering any Haskell programs in a 4KB demo
competition... The Haskell runtime engine alone is ~500KB, and that's
before you add any *functionallity*. o_O
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> It's rather incredible what you can squeeze into that amount of bytes.
Indeed. It used to be 32K was plenty for some rather sophisticated video
games. :-) Lots of the old arcade games had less than that, too.
--
Darren New / San Diego, CA, USA (PST)
Helpful housekeeping hints:
Check your feather pillows for holes
before putting them in the washing machine.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
For some reason I'm reminded of the demo of Uridium 2 I got to play on
my dad's Amiga.
You insert the disk into the drive, you hear a click, and instantly the
screen lights up in neon colours. First a set of blue bars appear, then
a set of thinner, transparent green bars scroll down over the top of
these, and then transparent red bars scroll up over both. The end result
is a myriad of colours. And all the time this is happening, electronic
music is playing, and the computer is still loading the *real* game from
disk.
Basically, the entire audio-visual candy-fest fits into the boot sector.
And well it might; the technicolour rainbow is just a trick of the
Amiga's copper ship, which modifies the image palette on each raster
scanline, yielding the effect of millions of colours at once, from a
bitmap that only actually handles a handful. (Notice that all the colour
bars are *horisontal*. This is not a coincidence.)
Ah, great days...
Damned TF2 takes 20 minutes to load up! o_O
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> John VanSickle <evi### [at] hotmailcom> wrote:
>> Halbert wrote:
>
>>> Why doesn't the rest of the world understand that?
>
>> Because I learned to program on a machine with 8k of memory. A byte
>> saved is a byte earned.
>
> You had a C compiler in a machine with 8k of memory? Which one was that?
I didn't say that I programmed in C on this machine, only that I learned
to program. The habit of being very stingy with memory use carries on.
Regards,
John
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
John VanSickle <evi### [at] hotmailcom> wrote:
> I didn't say that I programmed in C on this machine, only that I learned
> to program. The habit of being very stingy with memory use carries on.
Nowadays when I code I sometimes stumble into situations like:
"Hmm... This data will take over 100 megabytes of memory... Should
I worry? ... Nah. That's nothing."
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
andrel wrote:
> I'd like to see the specification that gave rise to that snipped of
> code. ;)
Umm. Write a contrived example showing that compact isn't always readable?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Raiford wrote:
> andrel wrote:
>> I'd like to see the specification that gave rise to that snipped of
>> code. ;)
>
> Umm. Write a contrived example showing that compact isn't always readable?
No that is more an assignment. A specification is where you specify what
the possible inputs are and what relations exist between input and
output...umm, ok, I know you were just kidding ;)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
