R
Richard Heathfield
[sticking to the C bits here]
jacob navia said:
Right. It isn't.
The evidence from the Standard is that, at most, it notices and reacts to a
null terminator in its input. But it certainly doesn't require one. If you
want to accuse me of arguing nonsense, you have to show that it's nonsense
to the satisfaction of others, not merely your own.
Some of the problems *you* perceive with the language, which is fine, but
not everyone shares your perception of what constitutes problems with C.
The fact that you're not GNU is irrelevant. The fact that you use Windows
is irrelevant. The fact that you don't GPL your code is irrelevant. When
you are criticised here, it is either for getting your C wrong or for
using this technical forum to advertise and promote your compiler.
On many occasions, these very people have pointed out problems with your
code or your advice but you've been unable to understand those problems.
It is you, not they, who struggle with technical discussions.
They're just being realistic. Are you prepared to use the library proposed
by Chris Tomasson? Even if you are, I'm not, because it doesn't meet my
needs. Standardisation is *really hard*, which is why ISO move so slowly.
And the reason it's really hard is that there are all these people saying
comp.std.c - and don't imagine for a moment that what your proposals for
"improvement" will meet with universal acclaim, any more than anyone
else's will.
jacob navia said:
Heathfield said that strncpy wasn't a function to copy strings.
Right. It isn't.
When presented with the evidence from the standard he waved
at it, and went on arguing nonsense.
The evidence from the Standard is that, at most, it notices and reacts to a
null terminator in its input. But it certainly doesn't require one. If you
want to accuse me of arguing nonsense, you have to show that it's nonsense
to the satisfaction of others, not merely your own.
I have developed a compiler system that tries to solve some of the
problems with the C language.
Some of the problems *you* perceive with the language, which is fine, but
not everyone shares your perception of what constitutes problems with C.
It is being distributed for free since 10 years.
But I am not GNU, and I use windows, and my code is not GPL, and many
other "very relevant" issues.
The fact that you're not GNU is irrelevant. The fact that you use Windows
is irrelevant. The fact that you don't GPL your code is irrelevant. When
you are criticised here, it is either for getting your C wrong or for
using this technical forum to advertise and promote your compiler.
There was never a technical discussion
because those people aren't able to discuss anything technical.
On many occasions, these very people have pointed out problems with your
code or your advice but you've been unable to understand those problems.
It is you, not they, who struggle with technical discussions.
Their reaction to the efforts of creating a library of abstract
data types is typical of their frame of mind. Nothing really substantive
but just "it will not work", each one should develop his own library
forever.
They're just being realistic. Are you prepared to use the library proposed
by Chris Tomasson? Even if you are, I'm not, because it doesn't meet my
needs. Standardisation is *really hard*, which is why ISO move so slowly.
And the reason it's really hard is that there are all these people saying
But as I said, I got tired of the endless polemic. Sadly, there is no
forum where people can discuss about the language, its shortcomings,
how to improve it, etc.
comp.std.c - and don't imagine for a moment that what your proposals for
"improvement" will meet with universal acclaim, any more than anyone
else's will.