Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!uwvax!tank!eecae!cps3xx!usenet
From: usenet@cps3xx.UUCP (Usenet file owner)
Newsgroups: comp.sys.amiga
Subject: Re: Yet another 1.4 wish
Message-ID: <3418@cps3xx.UUCP>
Date: 15 Jun 89 20:41:54 GMT
References: <16905@louie.udel.EDU> <1989Jun13.214755.5251@ziebmef.uucp>
Reply-To: porkka@frith.UUCP (Joe Porkka)
Organization: Michigan State University
Lines: 19

>In article <16905@louie.udel.EDU> MROBINSON@wash-vax.bbn.com writes:
>[dtsteen@dahlia.waterloo.edu wishes that the stack size become
> part of the executable]

I've had a neat idea about how do to this.

I think it would be a simple (I don't actually know) thing to do to
add an extra block type to execuables. Call it an extra block or
whatever. This block could contain standardized info about
stack size (like BSS blocks), virtual or protected memory support and
the like.
Once the loader knows about such blocks, then somebody should
be about to write a utility to tack that block on to existing
executables, so that regular users could fix their existing software
immediatly.
You could also use this block to store other application specific
information, like TOOLTYPES sort of info for CLI only programs.

This is an example of a short .signature   jap@frith.cl.msu.edu