rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Bengt Kleberg <bengt@softwell.se>
To: bengt@softwell.se, tjg@star.le.ac.uk
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: ifs substitution, how should it work?
Date: Thu, 18 May 2000 08:57:30 -0400	[thread overview]
Message-ID: <200005181257.OAA06188@trillian.softwell.se> (raw)

> From: Tim Goodwin <tjg@star.le.ac.uk>
> > ; x = ``(abc) {cmd...}
> > ; echo $x => 1a2b3 4c5

> If you want awk, you know where to find it.  :-)

Yes, but I had this little problem and suddenly realised that the mysterious 
``(abc) {cmd...}
actually might be used for something! I have never used it before.

> I don't think anything more complicated than single character field
> seperators belongs in a shell: particularly not rc.

OK. Would you consider making ``(abc)
a parse time error? only allow ifs=asd, or ifs=( a s d ), not ifs=(asd) too.
Or, as with the confusing

if ( {}  && {} ) {cmd...}
vs
if ( () && () ) {cmd...} 

document it.

> What's the actual problem you're trying to solve?

split a filename into directory, filename and suffix. the suffix should be allowed to have more than 1 character.
the idea is to make the previously emailed base_name function (made by Carlo Strozzi <carlos@linux.it>)
more like the os utility basename.


Best Wishes, Bengt
===============================================================
Everything aforementioned should be regarded as totally private
opinions, and nothing else. bengt@softwell.se
``His great strength is that he is uncompromising. It would make
him physically ill to think of programming in C++.''


             reply	other threads:[~2000-05-19 22:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-18 12:57 Bengt Kleberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-05-22  7:55 Bengt Kleberg
2000-05-22  8:53 ` Tim Goodwin
2000-05-19 22:10 Russ Cox
2000-05-18  8:12 Bengt Kleberg
2000-05-18 12:12 ` Tim Goodwin
2000-05-18  6:32 Byron Rakitzis
2000-05-16 11:22 Bengt Kleberg
2000-05-12 10:14 Bengt Kleberg
2000-05-15  9:27 ` Tim Goodwin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200005181257.OAA06188@trillian.softwell.se \
    --to=bengt@softwell.se \
    --cc=rc@hawkwind.utcs.toronto.edu \
    --cc=tjg@star.le.ac.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).