Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!news.iecc.com!nerds-end From: compilers@is-not-my.name Newsgroups: comp.compilers Subject: Re: Good practical language and OS agnostic text? Date: Sun, 22 Apr 2012 22:11:50 -0000 Organization: Compilers Central Lines: 24 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <12-04-075@comp.compilers> References: <12-04-056@comp.compilers> NNTP-Posting-Host: news.iecc.com X-Trace: leila.iecc.com 1335145369 35583 64.57.183.58 (23 Apr 2012 01:42:49 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Mon, 23 Apr 2012 01:42:49 +0000 (UTC) Keywords: interpreter Posted-Date: 22 Apr 2012 21:42:49 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com X-Received-Bytes: 2194 Xref: csiph.com comp.compilers:618 Uli Kusterer 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 > figure out what bytes your code gets compiled to (at worst by writing > a dummy assembler program and looking at what bytes show up between a > bunch of nop instructions whose bytes you know), you should be able to > at least get a basic working knowledge of how a compiler works. Just > write the naive approach of how you would design any program. 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. snip > Is that un-computer-sciencey enough? This blog post may help with the basics > of my code generation approach: > http://orangejuiceliberationfront.com/generating-machine-code-at-runtime/ (but > it's C, and Intel, and badly wrapped by the new theme of my blog). Thanks, I found your comments very useful. Seems like a good summary.