Re: [fpc-pascal] Re: command-line+Carbon template

2008-10-05 Thread Jonas Maebe
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

[fpc-pascal] Re: command-line+Carbon template

2008-10-05 Thread logrus
Thanks, Jonas -- I'll give that a try and report back. Bill > On 04 Oct 2008, at 22:48, Jonas Maebe <[EMAIL PROTECTED]> wrote: > > You could try running > > sudo fs_usage -w yourapp > > to see what exactly is going on at the file system level. Or you can > start your application and run "sudo fs

[fpc-pascal] Re: command-line+Carbon template

2008-10-05 Thread logrus
Marco -- 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-contained within that machine (the LISP code running

Re: [fpc-pascal] Re: command-line+Carbon template

2008-10-04 Thread Marco van de Voort
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

Re: [fpc-pascal] Re: command-line+Carbon template

2008-10-04 Thread Jonas Maebe
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

[fpc-pascal] Re: command-line+Carbon template

2008-10-04 Thread logrus
Hi, Danie -- 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 dummy file name (suffixed ".TMP"), then closin

[fpc-pascal] Re: command-line+Carbon template

2008-10-03 Thread Danie
On Ma, 2008-09-29 at 11:32 +0200, [EMAIL PROTECTED] wrote: : > Message: 2 > Date: Sun, 28 Sep 2008 08:44:46 -0700 (PDT) A bit late, but let's give it a try. : > Subject: [fpc-pascal] Re: command-line+Carbon template : > Be all that as it may, this whole Rube Goldberg runs gr

Re: [fpc-pascal] Re: command-line+Carbon template

2008-09-30 Thread Jonas Maebe
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

[fpc-pascal] Re: command-line+Carbon template

2008-09-30 Thread logrus
Thanks, Jonas -- 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 been written and closed is it renamed so

Re: [fpc-pascal] Re: command-line+Carbon template

2008-09-28 Thread Jonas Maebe
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

[fpc-pascal] Re: command-line+Carbon template

2008-09-28 Thread logrus
I didn't describe the problem I was experiencing becasue it seemed unlikely that anyone else would ever find themselves in this particular bind. That, and it didn't seem germane to the question I was asking -- namely, what to include in the project so as to access Carbon file routines from a comman