The somewhat unnerving behavior is that if you call OpenResFile and don't match it up with CloseResFile, the resource file is still open as long as MacPerl is still running! YIKES! (Please excuse my Bohemian pre-1990 Mac-API-speak. Well, whatever, that's the way Mac::* spells them too.) The various ResAttrs-returning calls may satisfy my other requirements. -joseph -- Joseph N. Hall, prop., 5 Sigma Productions mailto:joseph@5sigma.com Author, Effective Perl Programming . . . . . http://www.effectiveperl.com Perl Training . . . . . . . . . . . . . . . http://www.perltraining.com On Tue, 27 Jul 1999 01:30:08 -0400 wanderer@metamage.com (Joshua Juran) wrote: * It seems to me that the most reliable solution would be to modify MacPerl * (if necessary) so that it explicity calls UseResFile() and the * Get1Resource() family of calls (in between saving and restoring * CurResFile()), with the result that MacPerl would be unaffected by and * would not affect modifications to the resource chain by scripts, and then * implement those calls for MacPerl scripts to use. * * Josh ===== Want to unsubscribe from this list? ===== Send mail with body "unsubscribe" to macperl-request@macperl.org