> > 2) Also not sure I like the "architecture" name, since this is not really a > hardware architecture.
Address size? Another possibility is memory model, there could be different operand sizes than address sizes, like some JVMs do. > > 3) An actual hardware architecture one might be nice...not sure I want to > get into the issue of defining what is returned for that at this time. This > can easily be added later. It would be great if this could just match what the OS reports to us, like in uname -a. Windows must have a call for that also. > 4) Do we need some sort of byte-order indicator (i.e., endian-ness). Not > sure what values we're return for that. I think Big Endian or Little Endian, alternatively. MSB-first or LSB-first ------------------------------------------------------------------------------ _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
