Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!brutus.cs.uiuc.edu!lll-winken!muslix!jac
From: jac@muslix.llnl.gov (James Crotinger)
Newsgroups: comp.sys.amiga.tech
Subject: Re: What should be in future SKsh versions?
Message-ID: <40964@lll-winken.LLNL.GOV>
Date: 8 Dec 89 18:59:42 GMT
References: <13920018@hpfelg.HP.COM> <13920026@hpfelg.HP.COM>
Sender: usenet@lll-winken.LLNL.GOV
Reply-To: jac@muslix.UUCP (James Crotinger)
Organization: Lawrence Livermore National Laboratory/UC Davis
Lines: 8


  Why not do this: put the builtins into a library. Then sksh could
look for the library and use it if it's there, not use it if it ain't. 
Depending on how sksh works, this might make better use of memory too.
Also, you could release the specs for the library so others could
extend it if they liked.

  Jim