Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!munnari.oz.au!brolga!uqcspe!cs.uq.oz.au!warwick From: warwick@cs.uq.oz.au (Warwick Allison) Newsgroups: comp.sys.atari.st.tech Subject: Re: How store extra data at the end of an executable? Message-ID: <748@uqcspe.cs.uq.oz.au> Date: 12 Apr 91 02:44:01 GMT References: <5796@mcrware.UUCP> <615@uqcspe.cs.uq.oz.au> Sender: news@cs.uq.oz.au Reply-To: warwick@cs.uq.oz.au Lines: 25 wolfram@cip-s06.informatik.rwth-aachen.de (Wolfram Roesler) writes: >The problem is again that it's a real hard job for a prg to find it's >own executable. Why not: 1. Try ARGV/xARG 2. Try shell_read 3. Fail shell_read will work for Desktop run stuff. ARGV/xARG will work for stuff called from command line. If the user tries to use the program some other way (?) then that is there hard luck. Personally, I'd rather not put data into my executables anyway (what's wrong with separate files and environment variables? Much more flexible - we lose more flexibility in embedding data than we do by failing if the user calls our program by an obscure means.) Warwick. -- _--_|\ warwick@cs.uq.oz.au / * <-- Computer Science Department, \_.--._/ University of Queensland, v AUSTRALIA.