zsh-workers
 help / color / mirror / code / Atom feed
* Notes on bash(1)
@ 1998-12-09  3:25 Phil Pennock
  1998-12-09  9:01 ` Peter Stephenson
  0 siblings, 1 reply; 7+ messages in thread
From: Phil Pennock @ 1998-12-09  3:25 UTC (permalink / raw)
  To: Zsh Development Workers

I recently needed to check something in bash(1) and noticed some
interesting points in the manual.  I'm throwing them this way for
discussion/whatever.  Bash is 2.01.1(1)-release.

* bash has arrays.  'declare', 'local' & 'readonly' each accept '-a' to
  declare an array.  Is it reasonable to add '-a' to 'typeset'?  This
  would automatically duplicate the bash-ism.
  Further, would it be an idea to then deprecate 'set -A' which
  overloads parameter setting onto 'set'?

* ${parameter/pattern/string} and ${parameter//pattern/string}
  pattern is expanded as per pathname expansion.  Longest match of
  pattern against parameter is replaced with string.  Once for / and for
  all instances with //.  #pattern anchors to beginning, %pattern
  anchors to end.  string may be null.  Applied to an array, this works
  on each element.
  zsh has a some of this with the colon-modifier 's'.
  The anchors in particular are nice.  They would make it easy to fully
  replicate basename(1) without forking.  We can't currently (AFAIK)
  accurately duplicate $(basename file .ext) (think - filename: .ext.ex)
  % base=${var:t:s/%.ext//}

* ${parameter:offset} and ${parameter:offset:length} provide substring
  and array extraction.  Both length and offset are arithmetic
  expressions.  length>=0.  offset may be negative to measure from end.
  zsh notably has ${parameter[start,stop]} already.  How desirable is
  this alternate syntax, given that zsh allows history modifiers in the
  same place?  It doesn't look like there would be a conflict, provided
  zsh requires $[...] for variables there.  Testing, bash allows:
  $ foo=abcde; t=2; echo ${foo:t}
-- 
--> Phil Pennock ; GAT d- s+:+ a22 C++(++++) UL++++/I+++/S+++/H+ P++@ L+++
E-@ W(+) N>++ o !K w--- O>+ M V !PS PE Y+ PGP+ t-- 5++ X+ R !tv b++>+++ DI+ D+
G+ e+ h* r y?


^ permalink raw reply	[flat|nested] 7+ messages in thread
* Re:  Strange substring search behaviour
@ 1998-12-11  8:07 Sven Wischnowsky
  0 siblings, 0 replies; 7+ messages in thread
From: Sven Wischnowsky @ 1998-12-11  8:07 UTC (permalink / raw)
  To: zsh-workers


Peter Stephenson wrote:

> I'd quite like to rewrite the whole thing the way my original
> inclinations told me.  Any comments?  In other words, does anyone
> think they or anyone else is expecting to find the globally shortest
> match first?  Should I ask for a vote on zsh-users?

I think changing it would be a good idea (even though I guess it was
me who wrote the code with the strange behavior -- on the other side,
it just does what it was told ;-).

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~1998-12-12  7:47 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-12-09  3:25 Notes on bash(1) Phil Pennock
1998-12-09  9:01 ` Peter Stephenson
1998-12-09 17:04   ` PATCH: 3.1.5: bash ${.../old/new} Peter Stephenson
1998-12-10 15:52     ` Strange substring search behaviour Peter Stephenson
1998-12-09 19:43   ` PATCH: Docs out of sync Phil Pennock
1998-12-12  7:45     ` Bart Schaefer
1998-12-11  8:07 Strange substring search behaviour Sven Wischnowsky

Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).