Article View: gnu.bash.bug
Article #815functions and builtins
From: Drazen Borkovic
Date: Thu, 07 Dec 1989 10:15
Date: Thu, 07 Dec 1989 10:15
21 lines
1249 bytes
1249 bytes
I know that finding functions before builtins is probably more flexible, but sh (on SunOS 3.5) (and ksh) find the builtin first. Also, here are some things that would be nice to have. I know it is easy to talk about additions, but some of them shouldn't be too hard. 1. noclobber ( >| or >! would override) 2. variable PPID (parent process id) - shouldn't be too hard 3. variable RANDOM (initialize the seed when assigning to it) shouldn't be too hard 4. logout if idle time too long - shouldn't be too hard 5. [^characters] in file name generation (doesn't match characters) 6. arithmetic (like ksh) 7. ulimit Hard or Soft (Soft if you want to have a limit temporarily) shouldn't be too hard 8. when reporting errors when sourcing (.), line numbers would be nice Hope this helps. Drazen Borkovic drazen@vlsi.caltech.edu
Technical Details
Message-ID:
<8912071015.AA19603@vlsi.caltech.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!VLSI.CALTECH.EDU!drazenShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!VLSI.CALTECH.EDU!drazen From: drazen@VLSI.CALTECH.EDU (Drazen Borkovic) Newsgroups: gnu.bash.bug Subject: functions and builtins Message-ID: <8912071015.AA19603@vlsi.caltech.edu> Date: 7 Dec 89 10:15:56 GMT Sender: daemon@tut.cis.ohio-state.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 21