naughton@wind.Sun.COM (Patrick Naughton) (12/22/89)
How does eexec know when to stop? There is no indication how much data
follows the eexec, so how does it know to stop decrypting/executing the
file object and when to continue executing currentfile?
For example:
currentfile eexec
<lots of hex data>
cleartomark
{restore} if
Does eexec stop at the first non [0-9A-Fa-f] character?
Is there any way a filter can skip over all of the hex data?
-Patrick
______________________________________________________________________
Patrick J. Naughton ARPA: naughton@sun.com
Window Systems Group UUCP: ...!sun!naughton
Sun Microsystems, Inc. AT&T: (415) 336 - 1080amanda@mermaid.intercon.com (Amanda Walker) (12/23/89)
In article <129542@sun.Eng.Sun.COM>, naughton@wind.Sun.COM (Patrick Naughton) writes: > How does eexec know when to stop? When it hits and end of file. The usual way is to put "currefile closefile" at the end of your eexec-format stuff; since eexec uses a copy of the standard input stream, doing this won't actually shut down you AppleTalk connection... Amanda Walker InterCon Systems Corporation --