On 05 Oct 2008, at 13:31, [EMAIL PROTECTED] wrote:
If by "the two tests" you mean testing the FPC version vs. testing the
CodeWarrior version, then: yes, I'm pretty sure, since I'm running
them
both on the same machine (a Powerbook G4 laptop running Mac OSX
10.4.11).
The tests are self-cont
In our previous episode, [EMAIL PROTECTED] said:
> I'm not sure if you saw my most recent post, where I described what I was
> actually doing, in response to Jonas's concern that the LISP code might be
> trying to read the FPC-created file before it had been closed.
>
> I'm actually writing to a d
On 04 Oct 2008, at 22:48, [EMAIL PROTECTED] wrote:
I'm not sure if you saw my most recent post, where I described what
I was
actually doing, in response to Jonas's concern that the LISP code
might be
trying to read the FPC-created file before it had been closed.
I'm actually writing to a d
On 30 Sep 2008, at 21:54, [EMAIL PROTECTED] wrote:
Actually, I dealt with that potential source of anomalies way back
in the
original CodeWarrior version: the Pascal code opens and writes out
to the
file under a different name than the one the LISP code is looking for.
Only after the file's
On 28 Sep 2008, at 17:44, [EMAIL PROTECTED] wrote:
Be all that as it may, this whole Rube Goldberg runs great when
compiled
under CodeWarrior using MPW file i/o routines. With FPC's Turbo
routines,
I'm seeing some strange "race conditions" that lead me to believe
the FPC
version of the pro
