Re: [patch] First cut at TODO "allow add I4, I4, 3 instead of add_i_ic ..."

2001-09-14 Thread Uri Guttman
> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes: DS> At 10:33 PM 9/13/2001 -0400, Uri Guttman wrote: >> > "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes: >> DS> Actually, I'm expecting almost nothing to be written in pasm after DS> we get a working parser and compiler. We mi

Re: [patch] First cut at TODO "allow add I4, I4, 3 instead of add_i_ic ..."

2001-09-14 Thread Dan Sugalski
At 10:33 PM 9/13/2001 -0400, Uri Guttman wrote: > > "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes: > > DS> Actually, I'm expecting almost nothing to be written in pasm after > DS> we get a working parser and compiler. We might write template code > DS> for the compiler in it, but that'

Re: [patch] First cut at TODO "allow add I4, I4, 3 instead of add_i_ic ..."

2001-09-14 Thread Dan Sugalski
At 09:36 AM 9/14/2001 +0100, Leon Brocard wrote: >Dan Sugalski sent the following bits through the ether: > > > Actually, I'm expecting almost nothing to be written in pasm after we > get a > > working parser and compiler > >I am, as you may have noticed already, clearly a frustrated assembler >p

Re: [patch] First cut at TODO "allow add I4, I4, 3 instead of add_i_ic ..."

2001-09-14 Thread Leon Brocard
Dan Sugalski sent the following bits through the ether: > Actually, I'm expecting almost nothing to be written in pasm after we get a > working parser and compiler I am, as you may have noticed already, clearly a frustrated assembler programmer who's had to code high-level stuff for far too lon

Re: [patch] First cut at TODO "allow add I4, I4, 3 instead of add_i_ic ..."

2001-09-13 Thread Uri Guttman
> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes: DS> Actually, I'm expecting almost nothing to be written in pasm after DS> we get a working parser and compiler. We might write template code DS> for the compiler in it, but that's probably about it. Well, other DS> than the JAPHs tha

Re: [patch] First cut at TODO "allow add I4, I4, 3 instead of add_i_ic ..."

2001-09-13 Thread Dan Sugalski
At 09:42 AM 9/13/2001 -0400, Gregor N. Purdy wrote: >Dan -- > > > > * The recognition of register types means that you can't use labels > > > like 'I4'. It would be nice if registers and labels were in > > > different namespaces. > > > > I don't think this is necessary. Odds are almost n

Re: [patch] First cut at TODO "allow add I4, I4, 3 instead of add_i_ic ..."

2001-09-13 Thread Simon Cozens
On Wed, Sep 12, 2001 at 05:18:38PM -0400, Gregor N. Purdy wrote: > Attached is a diff for assemble.pl that does a somewhat messy job of > solving the problem posed in the TODO file. It does it by parsing > the root of each opcode when parsing the opcode table and creating a > hash with the opcode

Re: [patch] First cut at TODO "allow add I4, I4, 3 instead of add_i_ic ..."

2001-09-12 Thread Dan Sugalski
At 05:36 PM 9/12/2001 -0400, Gregor N. Purdy wrote: >All -- > >BTW, Here are some things to consider: > > * The recognition of register types means that you can't use labels > like 'I4'. It would be nice if registers and labels were in > different namespaces. I don't think this is neces

[patch] First cut at TODO "allow add I4, I4, 3 instead of add_i_ic..."

2001-09-12 Thread Gregor N. Purdy
All -- Attached is a diff for assemble.pl that does a somewhat messy job of solving the problem posed in the TODO file. It does it by parsing the root of each opcode when parsing the opcode table and creating a hash with the opcode root and the formal argument types (qualifiers) so that, e.g. $op