Re: Rob: More trouble with PD-source
Robert Craig wrote:
> No I can't. That's my point. The application seems to
> require a certain minimum level of speed from the
> interpreter. exw is fast enough. But the instant you
> turn on trace(3), it will start writing (and flushing)
> a line of text to a file for every single statement
> that it executes. That slows exw down by at least a
> couple of orders of magnitude, and makes it even
> slower than "exw eu.ex", which we know is too slow.
> Exactly why it crashes, we don't know, but it could
> have something to do with running multiple O/S threads,
> something that isn't really supported by Euphoria
> (as you are well aware 
).
Hmm... why does this code work with EXW + trace(3) and "exw eu netradio" +
trace(3)?:
StatusProc = routine_id("StatusProc")
chan = BASS_StreamCreateURL(urls[event], 0, BASS_STREAM_STATUS, StatusProc, 0)
but not this:
chan = BASS_StreamCreateURL(urls[event], 0, BASS_STREAM_STATUS,
routine_id("StatusProc"), 0)
Eu has to assign "StatusProc" before "chan" with each consecutive call to the
"DialogProc" subroutine, right? How would this be so different?
> By the way, I won two games of Language War last night
> using multi *tasking* in the official ex.exe (C backend) interpreter.
> So that project is coming along well. Maybe I'll release something
> in a week or so.
Kewl... are you planning to offer the gameplay recording feature too?
BTW, Open Watcom 1.4 is at it's second release candidate. It should be released
in time for Eu 3.0 building; perhaps you then can remove or comment out all the
Watcom 10.6 bug workaround code, that might be hindering back-end performance and
efficency a bit? Did you consider sacrificing a bit more memory for better
recursive performance with single task applications/libraries?
> Regards,
> Rob Craig
> Rapid Deployment Software
> <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a>
Regards,
Vincent
|
Not Categorized, Please Help
|
|
