Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| Questions about Bytecode Sean.D.Gillespie@gmail.com (Bison) (2007-04-18) |
| Re: Questions about Bytecode englere_geo@yahoo.com (Eric) (2007-04-19) |
| Re: Questions about Bytecode DrDiettrich1@aol.com (Hans-Peter Diettrich) (2007-04-19) |
| Re: Questions about Bytecode cfc@shell01.TheWorld.com (Chris F Clark) (2007-04-19) |
| Re: Questions about Bytecode Sean.D.Gillespie@gmail.com (Bison) (2007-04-20) |
| 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) |
| [5 later articles] |
| From: | Hans-Peter Diettrich <DrDiettrich1@aol.com> |
| Newsgroups: | comp.compilers |
| Date: | 19 Apr 2007 00:23:06 -0400 |
| Organization: | Compilers Central |
| References: | 07-04-061 |
| Keywords: | interpreter |
| Posted-Date: | 19 Apr 2007 00:23:06 EDT |
Bison wrote:
> More specifically, how would I represent literals, like String and
> numbers? The problem I have with this is, how could the VM
> differentiate between instructions and literal data? I've heard
> someone say that I could use a delimiter to mark start and end points.
This looks as if you intend to write out everything while parsing.
Consider using multiple sections and tables in the created file,
prepare them in memory or temporary files, and write out everything
when finished. Having everything in memory will allow to run the
parsed source immediately, without creating an precompiled file. Then
you'll immediately use the structures as required by the VM, apart
from what comes into mind while only parsing.
DoDi
Return to the
comp.compilers page.
Search the
comp.compilers archives again.