Name: Anonymous 2014-08-17 23:59
slow and dumb and inefficient
the C compiler goes error seeking
and as it passes
each line it parses
it calls...
functions and more functions
trying to break up expressions
into the thirteen levels of precedence
the ops have
how can I try to improve it?
hoard up the tokens in buffers?
how can I stop the thing looping?
I can't do it all just for free
we need money for R&D
just leave out one semicolon
the parasitic errors roll on
and scroll the line
of the screen each time
as it screams...
old-fashioned initialization
use equals and try simplifying
near line eleven
plus or minus seven
or so
searching through linked lists of half-full
hash tables a la Berkeley
looking for every single
ident symbol
it finds
how can I possibly graft it
onto a stack architecture?
functional disunity!
and how can I tell PCC
its not coding for PDPs
slow and dumb and inefficient
the C compiler goes error seeking
and as it passes
each line it parses
it calls...
the C compiler goes error seeking
and as it passes
each line it parses
it calls...
functions and more functions
trying to break up expressions
into the thirteen levels of precedence
the ops have
how can I try to improve it?
hoard up the tokens in buffers?
how can I stop the thing looping?
I can't do it all just for free
we need money for R&D
just leave out one semicolon
the parasitic errors roll on
and scroll the line
of the screen each time
as it screams...
old-fashioned initialization
use equals and try simplifying
near line eleven
plus or minus seven
or so
searching through linked lists of half-full
hash tables a la Berkeley
looking for every single
ident symbol
it finds
how can I possibly graft it
onto a stack architecture?
functional disunity!
and how can I tell PCC
its not coding for PDPs
slow and dumb and inefficient
the C compiler goes error seeking
and as it passes
each line it parses
it calls...