🚀 go-pugleaf

In article <852@laidbak.UUCP> tm@laidbak.UUCP (Takis Mercouris) writes:
 >I suspect that the Lattice C equivalent of pexec is the ridiculously
 >named shel_write, ...
............................
 
 >Is this indeed the equivalent of pexec, and if not which one is it?


  No, it isn't.  Not having Lattice for the ST, I can't tell you which
function to use, but I'm sure that one isn't it.  shel_write is an odd
GEM function which sets up an alternate program (other than the desk-top
or your current command shell) that will run on exit.

The function number $48 listed in the Abacus "internals" book is correct.

 >
 >Also, I looked in some usenet code (I think stmake) and the author seemed to
 >be encoding the length of the tail in its first byte. However, this is not
 >documented neither in my Lattice C manual (of course), nor in the Abacus
 >internals. 
 >

  No, it isn't documented anyplace I've looked, but that -is- the correct
way to call pexec.  The first byte of the command tail string must contain
the number of bytes in that string.  Some people have been passing a pointer
to the first byte after the program name which is normaly a space.  This is
fine as long as the programmer never uses a command tail longer than 32
bytes, but most people don't type command lines longer than that.  When they
finaly do try something that takes lots of typing, they (or some poor
unsuspecting user) gets fried when the system stops noticing anything
after the 32nd character...

  Hope this helps....

---
 John L. Stanley (john@viper.UUCP)
 Software Development Consultant - DynaSoft Systems
 UUCP: ...{amdahl,ihnp4,rutgers}!{meccts,dayton}!viper!john