Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| [5 earlier articles] |
| Re: Questions about Bytecode anton@mips.complang.tuwien.ac.at (2007-04-23) |
| Re: Questions about Bytecode ajohnson@mathworks.com (Andy Johnson) (2007-04-23) |
| Re: Questions about Bytecode DrDiettrich1@aol.com (Hans-Peter Diettrich) (2007-04-23) |
| Re: Questions about Bytecode haberg@math.su.se (2007-04-23) |
| Re: Questions about Bytecode chris.dollin@hp.com (Chris Dollin) (2007-04-23) |
| Re: Questions about Bytecode gah@ugcs.caltech.edu (glen herrmannsfeldt) (2007-04-25) |
| Re: Questions about Bytecode Peter_Flass@Yahoo.com (Peter Flass) (2007-04-26) |
| Re: Questions about Bytecode cdiggins@gmail.com (Christopher Diggins) (2007-04-26) |
| Re: Questions about Bytecode cdiggins@gmail.com (Christopher Diggins) (2007-04-26) |
| From: | Peter Flass <Peter_Flass@Yahoo.com> |
| Newsgroups: | comp.compilers |
| Date: | 26 Apr 2007 09:33:46 -0400 |
| Organization: | Road Runner High Speed Online http://www.rr.com |
| References: | 07-04-061 07-04-079 |
| Keywords: | VM, interpreter |
| Posted-Date: | 26 Apr 2007 09:33:46 EDT |
>>How would the typical structure of a bytecode-compiled file look?
>
> Why put the stuff in a file at all? Why not use the source code as
> on-disk representation and just compile to memory?
>
> In any case, if you want to have bytecode files, its structure is
> usually a serialized version of the in-memory representation. In one
> case I just used XDR routines to convert between the in the in-memory
> representation and the file format; a modern, but bloated equivalent
> would be to use XML as external representation.
If I were generating bytecode, I'd pick one which already as a VM to
interpret it, if possible. That is, Java or c# bytecode.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.