Re: encapsulating directory operations

Liste des GroupesRevenir à l c 
Sujet : Re: encapsulating directory operations
De : mutazilah (at) *nospam* gmail.com (Paul Edwards)
Groupes : comp.lang.c
Date : 25. May 2025, 23:12:03
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <10104jn$1jnb6$1@dont-email.me>
References : 1 2 3
User-Agent : Microsoft Outlook Express 6.00.2800.1106
"Keith Thompson" <Keith.S.Thompson+u@gmail.com> wrote in message
news:87y0uot8b7.fsf@nosuchdomain.example.com...
"Paul Edwards" <mutazilah@gmail.com> writes:

But neither of these are in C23. Nor were they in C90.
I want a slight variation to BOTH of those standards,
and for the next ISO standard - C30 or whatever -
to include that slight variation.
>
(I didn't previously state this, because I wasn't aware
of it, again)
>
I don't believe

You are correct to nuance things - an acknowledgement
that you can't predict the future with 100% certainty.

that you personally will have any influence over any
future C standard.  Your goals are too different from the goals of the
committee and those of the vast majority of people who care about C.

To me - this is a "mere challenge".

In this case, the plan is that my "add-on library", is so
small, and so useful, and hopefully so popular, that it
gets standardized into a theoretical C30, as well as
existing C90 libraries - including but not limited to
PDPCLIB - updated to include this new feature, that,
in hindsight, should have existed even in K&R C.
>
In my opinion that will never happen.

I am discussing a theoretical possibility, not making a
hard prediction.

I have no problem with whatever functionality you want to provide in
your PDPCLIB, and I'm willing to discuss some of it in technical terms.

Sure, thanks.

 It's just a library. It may or may not
depend on features of the C90 standard library.
>
No. It IS C90+.
>
I don't know what you mean by that.  If you mean that your PDPCLIB
library IS "C90+", that's fine; both are your invented terms.
But it's an odd choice of terminology.

You are guessing what I am talking about, so I will try to
explain.

No. PDPCLIB *will be* one of the possible theoretical
implementations of C90+.

Right now, it is pure C90.

Because right now, C90+ doesn't exist.

As such, there is no ESCAPE or any other define in any existing
or new header in PDPCLIB.

And that's the problem - I don't know where to add it.
As it turns out, the "defacto vague committee" made a
determination that "ESCAPE" is not an appropriate
name. I agree with the other members of the committee,
and the original proposer - ie you - agreed with that
"good catch".

That's a pretty good result to me.

If the other control characters are necessary for the
operation of microemacs - which I believe they are -
more than just ESCAPE needs to be added anyway.

Which header file and what names - that don't start
with "E"?

This is intended to be in the official ISO C standard for the next
1 million years.
>
That will not happen.

Even assuming that non-ESCAPE is never added to the
ISO C standard - and I'm not sure how you can predict
that - that doesn't stop it from being my INTENTION.

Actually influencing ISO is a separate exercise.
>
That will not happen either.

What do you mean by that? Not one single member of
the ISO committee will ever be influenced by a single
thing I say? Even if I join the committee myself? Even if
I bribe them? Even if I coerce them? Even if I stack the
ISO committee with my friends (after making some
friends - or bribing some people)?

It probably won't involve coercion.
>
But coercion wouldn't be required if the C90+ committee comes
up with something reasonable.
>
That sounds like a threat.  If it is, I suggest you stick it where the
sun don't shine.  But as far as I know you have no ability to carry out
your threat, so it's more pathetically amusing that frightening.

You are correct that I have no ability to coerce anyone at all.
Nor do I wish to do so even if I did. Nor did I even say it was
required.

It is a theoretical possibility.

Don't assume you can predict the future.

It never ever occurred to me that a US president would one
day mull over invading an erstwhile ally (Denmark) in order
to annex some territory (Greenland), that they are already on
as invited guests.

And if I am one day elected president of the USA, at the
same time as Chancellor of Germany, and a few other
places, you may well find 90% of the planet using it (or
at least, having it on their system).
>
See above regarding "where the sun don't shine".

I only need 51% of the vote, not 100% of the vote.

And I only said that 90% of the planet may be using
my ecosystem, not 100%.

You have no personal control over either those 51% or
those 90%.

We're both lobbying for their support.

"Don't vote for Paul - he's going to replace the ISO
C committee just so that he can run microemacs!!!".

I don't think most voters will care as much about that
issue as you apparently do. But we'll see ...

And again - I don't actually care if I succeed. I'm happy
to have just tried.

Did you see "One Flew Over the Cuckoo's Nest"?

The guy tries to lift the water cooler. It doesn't really
bother him that he failed.

A big Indian guy succeeded.

Maybe one day a big Indian guy will read comp.lang.c
and complete what I was unable to complete.

BFN. Paul.



Date Sujet#  Auteur
20 May07:06 * encapsulating directory operations160Paul Edwards
20 May08:27 +* Re: encapsulating directory operations21Lawrence D'Oliveiro
20 May10:33 i`* Re: encapsulating directory operations20Paul Edwards
21 May01:10 i `* Re: encapsulating directory operations19Lawrence D'Oliveiro
21 May01:23 i  `* Re: encapsulating directory operations18Paul Edwards
21 May04:37 i   `* Re: encapsulating directory operations17Lawrence D'Oliveiro
21 May11:00 i    +* Re: encapsulating directory operations3Paul Edwards
22 May07:49 i    i`* Re: encapsulating directory operations2Lawrence D'Oliveiro
22 May08:02 i    i `- Re: encapsulating directory operations1Kaz Kylheku
22 May00:51 i    `* Re: encapsulating directory operations13James Kuyper
22 May06:04 i     `* Re: encapsulating directory operations12Lawrence D'Oliveiro
22 May19:13 i      `* Re: encapsulating directory operations11James Kuyper
22 May23:46 i       `* Re: encapsulating directory operations10Lawrence D'Oliveiro
23 May00:07 i        `* Re: encapsulating directory operations9James Kuyper
23 May00:15 i         `* Re: encapsulating directory operations8Kaz Kylheku
23 May00:26 i          +* Re: encapsulating directory operations3Paul Edwards
23 May01:44 i          i+- Re: encapsulating directory operations1Kaz Kylheku
24 May03:26 i          i`- Re: encapsulating directory operations1Lawrence D'Oliveiro
23 May01:10 i          `* Re: encapsulating directory operations4James Kuyper
23 May03:08 i           `* Re: encapsulating directory operations3Kaz Kylheku
24 May00:29 i            `* Re: encapsulating directory operations2James Kuyper
24 May01:08 i             `- Re: encapsulating directory operations1Kaz Kylheku
20 May10:18 +* Re: encapsulating directory operations58Keith Thompson
20 May10:33 i+* Re: encapsulating directory operations14Richard Heathfield
20 May10:45 ii+- Re: encapsulating directory operations1Paul Edwards
20 May12:42 ii+- Re: encapsulating directory operations1David Brown
20 May14:55 ii+* Re: encapsulating directory operations7Kaz Kylheku
20 May15:05 iii`* Re: encapsulating directory operations6Richard Heathfield
20 May15:09 iii +* Re: encapsulating directory operations2Muttley
20 May15:15 iii i`- Re: encapsulating directory operations1Paul Edwards
20 May15:48 iii `* Re: encapsulating directory operations3Paul Edwards
20 May16:02 iii  `* Re: encapsulating directory operations2Richard Heathfield
20 May16:28 iii   `- Re: encapsulating directory operations1Paul Edwards
23 May13:43 ii`* Re: encapsulating directory operations4Tim Rentsch
23 May14:27 ii `* Re: encapsulating directory operations3Richard Heathfield
24 May06:32 ii  `* Re: encapsulating directory operations2Tim Rentsch
24 May06:54 ii   `- Re: encapsulating directory operations1Richard Heathfield
20 May10:36 i`* Re: encapsulating directory operations43Paul Edwards
20 May13:23 i +* Re: encapsulating directory operations39David Brown
20 May14:47 i i`* Re: encapsulating directory operations38Paul Edwards
20 May15:37 i i +* Re: encapsulating directory operations10Richard Heathfield
20 May16:11 i i i`* Re: encapsulating directory operations9Paul Edwards
20 May16:43 i i i `* Re: encapsulating directory operations8Richard Heathfield
20 May22:15 i i i  +* Re: encapsulating directory operations2Paul Edwards
20 May23:50 i i i  i`- Re: encapsulating directory operations1Kaz Kylheku
21 May02:11 i i i  +- Re: encapsulating directory operations1Lawrence D'Oliveiro
21 May03:40 i i i  `* Re: encapsulating directory operations4James Kuyper
21 May05:50 i i i   `* Re: encapsulating directory operations3Richard Heathfield
21 May09:06 i i i    `* Re: encapsulating directory operations2David Brown
21 May09:27 i i i     `- Re: encapsulating directory operations1Richard Heathfield
20 May17:19 i i `* Re: encapsulating directory operations27David Brown
20 May17:43 i i  +* Re: encapsulating directory operations6Richard Heathfield
20 May18:14 i i  i+* Re: encapsulating directory operations4Kaz Kylheku
20 May18:20 i i  ii`* Re: encapsulating directory operations3Richard Heathfield
20 May19:50 i i  ii +- Re: encapsulating directory operations1Richard Heathfield
20 May20:34 i i  ii `- Re: encapsulating directory operations1Kaz Kylheku
21 May09:09 i i  i`- Re: encapsulating directory operations1David Brown
20 May17:51 i i  +- Re: encapsulating directory operations1Kaz Kylheku
20 May18:09 i i  +* Re: encapsulating directory operations2Richard Heathfield
20 May19:34 i i  i`- Re: encapsulating directory operations1Richard Heathfield
20 May22:41 i i  +* Re: encapsulating directory operations4Paul Edwards
20 May23:02 i i  i+- Re: encapsulating directory operations1Keith Thompson
21 May02:05 i i  i`* Re: encapsulating directory operations2Lawrence D'Oliveiro
21 May10:23 i i  i `- Re: encapsulating directory operations1Paul Edwards
20 May22:51 i i  +* Re: encapsulating directory operations9Paul Edwards
21 May05:31 i i  i`* Re: encapsulating directory operations8Richard Heathfield
21 May11:08 i i  i `* Re: encapsulating directory operations7Paul Edwards
21 May11:28 i i  i  +- Re: encapsulating directory operations1Richard Heathfield
21 May16:00 i i  i  `* Re: encapsulating directory operations5David Brown
21 May16:37 i i  i   `* Re: encapsulating directory operations4Richard Heathfield
21 May18:21 i i  i    +- Re: encapsulating directory operations1Michael S
22 May11:37 i i  i    `* Re: encapsulating directory operations2James Kuyper
22 May18:53 i i  i     `- Re: encapsulating directory operations1Kaz Kylheku
20 May23:09 i i  +- Re: encapsulating directory operations1Paul Edwards
21 May09:27 i i  `* Re: encapsulating directory operations3David Brown
21 May11:46 i i   `* Re: encapsulating directory operations2Paul Edwards
21 May15:46 i i    `- Re: encapsulating directory operations1David Brown
21 May01:12 i `* Re: encapsulating directory operations3Lawrence D'Oliveiro
21 May01:25 i  `* Re: encapsulating directory operations2Paul Edwards
21 May02:03 i   `- Re: encapsulating directory operations1Lawrence D'Oliveiro
20 May14:53 +* Re: encapsulating directory operations75Kaz Kylheku
20 May15:12 i`* Re: encapsulating directory operations74Paul Edwards
20 May22:41 i `* Re: encapsulating directory operations73Keith Thompson
20 May23:38 i  `* Re: encapsulating directory operations72Paul Edwards
21 May00:09 i   +* Re: encapsulating directory operations5Paul Edwards
21 May00:22 i   i+- Re: encapsulating directory operations1Keith Thompson
21 May01:18 i   i+* Re: encapsulating directory operations2Kaz Kylheku
21 May01:31 i   ii`- Re: encapsulating directory operations1Paul Edwards
21 May02:02 i   i`- Re: encapsulating directory operations1Lawrence D'Oliveiro
21 May00:18 i   +* Re: encapsulating directory operations57Keith Thompson
21 May00:57 i   i+* Re: encapsulating directory operations49Paul Edwards
21 May06:41 i   ii`* Re: encapsulating directory operations48Keith Thompson
21 May11:41 i   ii +* Re: encapsulating directory operations43Paul Edwards
21 May19:06 i   ii i+* Re: encapsulating directory operations40Keith Thompson
21 May19:22 i   ii ii+- Re: encapsulating directory operations1Keith Thompson
22 May22:10 i   ii ii+* Re: encapsulating directory operations35Paul Edwards
22 May23:32 i   ii iii+* Re: encapsulating directory operations33Keith Thompson
23 May00:16 i   ii iiii+* Re: encapsulating directory operations18Paul Edwards
23 May02:38 i   ii iiiii+* Re: encapsulating directory operations5Keith Thompson
25 May23:12 i   ii iiiiii`* Re: encapsulating directory operations4Paul Edwards
25 May23:34 i   ii iiiiii `* Re: encapsulating directory operations3Keith Thompson
23 May03:28 i   ii iiiii+* Re: encapsulating directory operations2Kaz Kylheku
23 May06:08 i   ii iiiii`* Re: encapsulating directory operations10Janis Papanagnou
23 May16:09 i   ii iiii`* Re: encapsulating directory operations14Richard Harnden
22 May23:44 i   ii iii`- Re: encapsulating directory operations1Paul Edwards
22 May23:06 i   ii ii`* Re: encapsulating directory operations3Paul Edwards
21 May20:31 i   ii i`* Re: encapsulating directory operations2Kaz Kylheku
22 May22:52 i   ii `* Re: encapsulating directory operations4Paul Edwards
21 May03:21 i   i`* Re: encapsulating directory operations7Kaz Kylheku
21 May03:26 i   +* Re: encapsulating directory operations7James Kuyper
21 May22:19 i   `* Re: encapsulating directory operations2Waldek Hebisch
21 May03:35 +* Re: encapsulating directory operations3Janis Papanagnou
22 May19:34 +- Re: encapsulating directory operations1Bonita Montero
25 May06:10 `- Re: encapsulating directory operations1Tim Rentsch

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal