> And the problem is that this hits a fast path in the classical news spool
> layout article create path. The code for this assumes that you have
> articles in the range X to Y, and you just got a new article, so you write
> a file called /var/spool/news/group/name/Y+1. You really do not want to
Warning: No kernel related stuff inside.
[EMAIL PROTECTED] (Rik van Riel) wrote on 26.03.01 in
<[EMAIL PROTECTED]>:
> On Mon, 26 Mar 2001, John Cowan wrote:
> > In fact this has come up before: in Usenet software, which has to
> > differentiate between an article and a sub-newsgroup. An
Warning: No kernel related stuff inside.
[EMAIL PROTECTED] (Rik van Riel) wrote on 26.03.01 in
[EMAIL PROTECTED]:
On Mon, 26 Mar 2001, John Cowan wrote:
In fact this has come up before: in Usenet software, which has to
differentiate between an article and a sub-newsgroup. An article
And the problem is that this hits a fast path in the classical news spool
layout article create path. The code for this assumes that you have
articles in the range X to Y, and you just got a new article, so you write
a file called /var/spool/news/group/name/Y+1. You really do not want to
John Cowan <[EMAIL PROTECTED]>:
> > If CML2 is adopted and I become the config system maimtainer,
>^
> Typo-ROTFL!
Of such errors are linguistic innovations made. I wonder if this one
will propagate enough that I have to put it in the
Eric S. Raymond wrote:
> If CML2 is adopted and I become the config system maimtainer,
^
Typo-ROTFL!
--
There is / one art || John Cowan <[EMAIL PROTECTED]>
no more / no less || http://www.reutershealth.com
to do
Rik van Riel <[EMAIL PROTECTED]>:
> What's wrong with using the _file type_ for these things ?
I don't understand that.
> Conversely, why can't CML2 use the CONFIG_ prefix to
> determine if a symbol is a configuration option, like
> we're doing now?
I do understand this. Greg Banks pointed
On Mon, 26 Mar 2001, John Cowan wrote:
> esr scripsit:
>
> > it needs is more overhead, and (2) interpreting symbols with leading digits
> > as nonnumeric tokens is just *wrong*. Ugh. Violates the Principle of Least
> > Surprise big-time.
>
> In fact this has come up before: in Usenet
esr scripsit:
> I could have done this, allowing tokens to be recognized as numeric only
> if all chars are digits. I didn't, for two reasons: (1) Lexical analysis
> is, as it turns out, a hotspot in the CML2 compiler code -- the last thing
> it needs is more overhead, and (2) interpreting
esr scripsit:
I could have done this, allowing tokens to be recognized as numeric only
if all chars are digits. I didn't, for two reasons: (1) Lexical analysis
is, as it turns out, a hotspot in the CML2 compiler code -- the last thing
it needs is more overhead, and (2) interpreting symbols
On Mon, 26 Mar 2001, John Cowan wrote:
esr scripsit:
it needs is more overhead, and (2) interpreting symbols with leading digits
as nonnumeric tokens is just *wrong*. Ugh. Violates the Principle of Least
Surprise big-time.
In fact this has come up before: in Usenet software, which
Rik van Riel [EMAIL PROTECTED]:
What's wrong with using the _file type_ for these things ?
I don't understand that.
Conversely, why can't CML2 use the CONFIG_ prefix to
determine if a symbol is a configuration option, like
we're doing now?
I do understand this. Greg Banks pointed it out
Eric S. Raymond wrote:
If CML2 is adopted and I become the config system maimtainer,
^
Typo-ROTFL!
--
There is / one art || John Cowan [EMAIL PROTECTED]
no more / no less || http://www.reutershealth.com
to do /
John Cowan [EMAIL PROTECTED]:
If CML2 is adopted and I become the config system maimtainer,
^
Typo-ROTFL!
Of such errors are linguistic innovations made. I wonder if this one
will propagate enough that I have to put it in the Jargon
Jeff Garzik <[EMAIL PROTECTED]>:
> There is no good reason to restrict the CML2 identifier namespace.
I've already listed a couple of good reasons. As Peter said, maintanicus
selector est.
--
http://www.tuxedo.org/~esr/">Eric S. Raymond
No one who's seen it in action can say
Keith Owens wrote:
> That just leaves the 17 names of the form CONFIG_[0-9]*. Only the 8139
> is likely to affect outside the kernel and the argument that renaming
> config options might affect external packages does not hold. The
> recent aic7xxx change broke pcmcia on 2.2 kernels but we can
On Mon, 26 Mar 2001 02:09:02 -0500,
"Eric S. Raymond" <[EMAIL PROTECTED]> wrote:
>Jeff Garzik <[EMAIL PROTECTED]>:
>> If we are moving to CML2 in 2.5, I see no point in big CML1 cleanups.
>
>Yes, I know, that's what I said about Peter's DERIVED patch a week ago.
Hey, that was my DERIVED patch,
Eric Raymond writes:
> (1) 19 of the 39 changes fix things that are outright bugs even in CML1.
> These should not be allowed to persist in the stable branch.
I think that things that are bugs in CML1, on its own terms, are
worth fixing in 2.4.
Michael
-
To unsubscribe from this list: send
Eric Raymond writes:
(1) 19 of the 39 changes fix things that are outright bugs even in CML1.
These should not be allowed to persist in the stable branch.
I think that things that are bugs in CML1, on its own terms, are
worth fixing in 2.4.
Michael
-
To unsubscribe from this list: send
On Mon, 26 Mar 2001 02:09:02 -0500,
"Eric S. Raymond" [EMAIL PROTECTED] wrote:
Jeff Garzik [EMAIL PROTECTED]:
If we are moving to CML2 in 2.5, I see no point in big CML1 cleanups.
Yes, I know, that's what I said about Peter's DERIVED patch a week ago.
Hey, that was my DERIVED patch, not
Jeff Garzik [EMAIL PROTECTED]:
There is no good reason to restrict the CML2 identifier namespace.
I've already listed a couple of good reasons. As Peter said, maintanicus
selector est.
--
a href="http://www.tuxedo.org/~esr/"Eric S. Raymond/a
No one who's seen it in action
Keith Owens wrote:
That just leaves the 17 names of the form CONFIG_[0-9]*. Only the 8139
is likely to affect outside the kernel and the argument that renaming
config options might affect external packages does not hold. The
recent aic7xxx change broke pcmcia on 2.2 kernels but we can work
22 matches
Mail list logo
