From: craig@jcb-sc.com
To: zack@rabi.columbia.edu
Cc: craig@jcb-sc.com
Subject: Re: gcc driver language: poll
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <19990325194033.6695.qmail@deer> (raw)
Message-ID: <19990331234600.QqAaN0enabJa2ZoFRYEsOkQv1g5YmwUrOrWEgcHVBP4@z> (raw)
In-Reply-To: <199903232236.RAA19048@blastula.phys.columbia.edu>
I don't see any obvious problems with the new proposal, but am not
sufficiently "in touch" with the world of specs to want anyone to
take that as any kind of endorsement. One question:
>~X* all switches beginning with -X
>~X(*) same as ~X*, but delete -X
Would it be reasonable to replace the second form with this?
>~X?* same as ~X*, excluding -X
Maybe I misunderstand "delete". Also, I'm thinking in terms of the
syntax looking a bit more like wildcarding than it currently does.
(That might or might not be a good thing in the long run.)
Generally, though, I think `(*)' is syntactically inappropriate to
mean one or more following characters. Perhaps another character
could be found, etc.
tq vm, (burley)
next prev parent reply other threads:[~1999-03-31 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-23 14:36 Zack Weinberg
[not found] ` < 199903232236.RAA19048@blastula.phys.columbia.edu >
1999-03-25 14:09 ` Richard Henderson
1999-03-31 23:46 ` Richard Henderson
1999-03-25 15:56 ` craig [this message]
1999-03-31 23:46 ` craig
1999-03-31 23:46 ` Zack Weinberg
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=19990325194033.6695.qmail@deer \
--to=craig@jcb-sc.com \
--cc=zack@rabi.columbia.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).