Path: utzoo!news-server.csri.toronto.edu!rutgers!dimacs.rutgers.edu!mips!samsung!munnari.oz.au!brolga!bunyip.cc.uq.oz.au!qut.edu.au!lunnon
From: lunnon@qut.edu.au
Newsgroups: comp.sys.atari.st
Subject: Re: What's the BEST CLI for the ST
Message-ID: <1991Mar14.155746.25333@qut.edu.au>
Date: 14 Mar 91 20:57:46 GMT
References: <1991Mar13.123427.11100@doe.utoronto.ca>
Organization: Queensland University of Technology
Lines: 38

In article <1991Mar13.123427.11100@doe.utoronto.ca>, david@doe.utoronto.ca (David Megginson) writes:
> 
> In <111@uqcspe.cs.uq.oz.au>, warwick@cs.uq.oz.au writes:
>> 
>> 	Sounds like a TSR is necessary - so instruction space can be shared.
>> Has anyobdy done any work on this idea?
>> 
> 
> Eric Smith plans to add shared text segments to a later version of MiNT.
> I am not sure exactly what this involves, but I imagine that he will come
> up with some way of identifying a program which is already running
> (same path and checksum?), and swap the .bss and .data in and out with
> task changes. This would slow down MiNT a bit, but with programs like
> bash(1) which is mostly .text, it would save a lot of memory. Comments?
> Suggestions? If someone wants to write this themselves, it will show
> up faster (Eric shouldn't have to do everything himself).
> 

This would be nice but why doesn't someone take a standard ansi C library
and make a shareable version taht can be loaded at boot time and there
after used ( Via a trap for example ) then with the appropriate binding
the text size of executable could be reduced by the size of the linked
library. How about a coff loader for TOS and dynamic linking :-)

BOB
R.Lunnon@qut.edu.au




> 
> David
> 
> -- 
> ////////////////////////////////////////////////////////////////////////
> /  David Megginson                      david@doe.utoronto.ca          /
> /  Centre for Medieval Studies          meggin@vm.epas.utoronto.ca     /
> ////////////////////////////////////////////////////////////////////////