<x-flowed>At 19:24 +0100 2/23/99, Matthias Neeracher wrote: > In article > <3.0.3.32.19990223115812.00f52008@mailhost.cam.harlequin.co.uk>, > Peter Westlake <peter@harlequin.co.uk> writes: >> Is MacPerl 5.2.0r4 compatible with Mac OS 8.1 and 8.5.1? > > Definitely. It was *developed* under 8.1, and I run it daily under 8.5.1. > >> When I run the script the second time, >> it crashes almost at once. This is the MPW tool version of >> Perl 5.2.0r4, with MPW Shell 3.5d6, running on Mac OS 8.1 and >> 8.5.1 (most of the testing was done on 8.5.1). > > I've seen this before and it seems to be related to MPW. Last time I tried to > track it down, the problem disappeared, and I'm not naturally given > to running > AppleScripts. I'll have another look. Running the MPW command flush (no parameters) between executions of the MacPerl script in MPW (/Toolserver) might be useful, at least to provide information. flush removes cached MPW tools from memory, so that the next execution would have a fresh start. If flush helps, one might suspect a global variable which perhaps shouldn't be. --------- I'm also a little concerned about the "bare" display dialog "..." command in the script. It would be interesting to direct that to some application, such as the ever-handy Finder, to see whether the behavior changes. As is, it should be running in the context of the MacPerl runtime app (I think)...and the presence of both the MacPerl tool and the MacPerl runtime on the machine might somehow not like that. Putting the display dialog "..." inside a tell app "Finder"... block is a quick test...but I'm leaning more toward the effects of flush. --john -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA Give a man a fish and you feed him for a day. Teach him to fish, and you get rid of him for the weekend. ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch </x-flowed>