1. Re: mac.ex
- Posted by Pete Eberlein <xseal at HARBORSIDE.COM> Sep 23, 1998
- 349 views
> WHen developping a big or complicated program, it usually consists of > multiple parts, some less dificult than others. Fox example, when Robert > wrote ex.exe he would prolly started with a basic preproccesor, which he > tested until he knew for sure, it did what it did. Then I assume he wrote > the sequence engine.. same testing here.. then some of the built-in > routines, some testing, then the machine proc/functions (graphics, and > stuff) and finally the euphoria includes. For those who are curious, PEU started with the sequence engine *first*, and then the byte-code interpreter (actually just a loop calling a function pointer) and then came the parsing of actual source code. Having sequences at first helped during development, because I could code in C with Euphoria-style thought processes. David Cuny started his Gnuphoria with the parser first, and had his sequence engine designed separately to be merged in later. Another thing that might be of interest to the OS folk, is that it might not be too difficult to add multi-threading capability to PEU. The interpreter could easily switch between which set of bytecodes to execute at any given time. How to start another thread is the question... (from an .ex file most likely) and whether or not each thread shares the same global variables... things could get messy. And if I can ever get PEU to compile and run with WATCOM, Hawke can compile with all the optimization settings he pleases. Open source is so cool... to bad the Portable part of PEU isn't up to par, presently it is pretty poopy. Work on fixing that should start soon. [discard] I got to thinking that assigning to an object would be the most efficient way to ignore a result. This is what I've used most often anyway. object junk junk = graphics_mode(-1) But when I'm too lazy to declare of variable for a quick value I need to use later, I've been known to do something like: junk = complex_calculation() junk = junk + 0 * wait_key() junk = junk + graphics_mode(-1) ? junk I need a write-only variable so I'm not tempted to do this... or a place where I can put my junk and not be able to dig through it later. Of course, if I had good programming habits, none of this would be a problem. _______ ______ _______ ______ [ _ \[ _ ][ _ _ ][ _ ] [/| [_] |[/| [_\][/ | | \][/| [_\] | ___/ | _] | | | _] [\| [/] [\| [_/] [\| |/] [\| [_/] [_____] [______] [_____] [______] xseal at harborside.com ICQ:13466657 http://www.harborside.com/home/x/xseal/euphoria/