From: | "BartC" <bc@freeuk.com> |
Newsgroups: | comp.compilers |
Date: | Mon, 23 Apr 2012 18:41:26 +0100 |
Organization: | A noiseless patient Spider |
References: | 12-04-056 12-04-075 |
Keywords: | parse, interpreter, history |
Posted-Date: | 24 Apr 2012 12:07:35 EDT |
<compilers@is-not-my.name> wrote
> Uli Kusterer <ulimakesacompiler@nospam.googlemail.com> wrote:
>
>> IMO if you know assembler or BASIC and general algorithms (i.e. you
>> could implement a binary tree and walk its nodes), and you can somehow
> I have written a few interpreters and I thought about winging it but I
> realize there is a science to compiling and there are right and wrong ways
> to do things. I would like to do things the right way but maybe with my
> weak background and broken undergrad CS degree that is expecting too much.
I'm intrigued as to why you think writing compilers is a science but writing
interpreters isn't? Interpreters can include a big chunk of what's in a
compiler, and these days I think can be just as challenging.
And I don't know about right ways and wrong ways to write programs, but for
compilers there are probably formal and informal ways of implementing one.
(Naturally, I've always done things informally; it wasn't my job to write
compilers, they were just useful tools I created. But despite probably being
considered toys, they were used to write actual commercial applications and
to earn a living with!)
BTW I don't think CS degrees existed when compilers started being created.
--
Bartc
Return to the
comp.compilers page.
Search the
comp.compilers archives again.