Re: Good practical language and OS agnostic text?

"BartC" <bc@freeuk.com>
Mon, 23 Apr 2012 18:41:26 +0100

          From comp.compilers

Related articles
[39 earlier articles]
Re: Good practical language and OS agnostic text? compilers@is-not-my.name (2012-04-22)
Re: Good practical language and OS agnostic text? compilers@is-not-my.name (2012-04-22)
Re: Good practical language and OS agnostic text? tk@ic.unicamp.br (Tomasz Kowaltowski) (2012-04-22)
Re: Good practical language and OS agnostic text? cr88192@hotmail.com (BGB) (2012-04-22)
Re: Good practical language and OS agnostic text? compilers@is-not-my.name (2012-04-22)
Re: Good practical language and OS agnostic text? gah@ugcs.caltech.edu (glen herrmannsfeldt) (2012-04-22)
Re: Good practical language and OS agnostic text? bc@freeuk.com (BartC) (2012-04-23)
Re: Good practical language and OS agnostic text? compilers@is-not-my.name (2012-04-23)
Re: Good practical language and OS agnostic text? basile@starynkevitch.net (2012-05-02)
Re: Good practical language and OS agnostic text? johann@2ndquadrant.com (Johann 'Myrkraverk' Oskarsson) (2012-06-06)
Re: Good practical language and OS agnostic text? sinu.nayak2001@gmail.com (Srinivas Nayak) (2012-06-16)
| List of all articles for this month |
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


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.