Re: comp.lang.c Answers (Abridged) to Frequently Asked Questions (FAQ)


Michael Wojcik wrote:
> In article <1128878126.638196.265110@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, "mensanator@xxxxxxx" <mensanator@xxxxxxx> writes:
> > Michael Wojcik wrote:
> > > In article <1128840360.746856.27220@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, "mensanator@xxxxxxx" <mensanator@xxxxxxx> writes:
> > > > Michael Wojcik wrote:
> > > > > In article <1128746506.876706.141010@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, "mensanator@xxxxxxx" <mensanator@xxxxxxx> writes:
> > > > > >
> > > > > > People are constantly saying to read the FAQ before asking a
> > > > > > stupid question. But when you do, they turn around and tell
> > > > > > you not to:
> > > > > >
> > > > > > Timothy Little wrote:
> > > > > > >
> > > > > > > It's certainly not relevant for any of the C libraries I use.
> > > > >
> > > > > At any rate, I do not see anywhere in the posted text where anyone
> > > > > claimed you shouldn't read the FAQ.
> > > >
> > > > You didn't see his opinion that it should be removed from the FAQ?
> > >
> > > It certainly wasn't in anything that you quoted in your post.
> >
> > No, it wasn't in the part that YOU quoted. Here is the restored quote:
>
> Nor is it in the part you quoted.
>
> > <quote>
> > Timothy Little wrote:
> > > It's certainly not relevant for any of the C libraries I use. I
> > > expect the FAQ is still there in case someone is using an ancient
> > > library routine that still has that flaw. (Or just because nobody has
> > > bothered to remove it from the FAQ)
> > </quote>
>
> Nowhere in there does Timothy say that it should be removed. He
> claimed that it might be in the FAQ because it hadn't been removed,
> which is a very different claim (and a redundant one - obviously,
> if it's there, it hasn't been removed).
>
> > If you're going to snip irrelevant parts of the message, fine.
> > But don't then try to claim that they were never there.
>
> They never were.
>
> > > > > One person opined that one item
> > > > > in it did not apply to the implementations he uses.
> > > >
> > > > No, he opined that it applies to ALL implementations
> > >
> > > What part of "I use" in Timothy's reply did you not understand? Did
> > > you believe he was claiming he's used every implementation?
> >
> > I did say he's used every implementation. But it follows from his
> > statement "because no one has bothered to remove it from the FAQ"
> > that the issue is no longer applicable to ANY compiler.
>
> That most certainly does not follow. You're leaping to a completely
> unwarranted conclusion.


Ok, forget that, it's not important.


>
> > > > So maybe not everyone uses the same implementation.
> > >
> > > Obviously. That, indeed, was my point. What's yours?
> >
> > I'm asking the opinion of those more knowledgeable about c programming
> > whether the warnimgs about rand() still warrant inclusion in the FAQ.
>
> In my opinion, yes; and I understand that to be Keith's position as
> well. (Whether either of us qualify as "more knowledgeable" I'll let
> you judge.)
>
> That's the main reason why I claimed Timothy's response was misleading.
> The FAQ entry, as written, is perfectly correct; and while it may not
> apply to any implementations he has used (whatever those are, and we
> only have his word on that), we have no guarantees about other
> implementations - old or new.
>
> > I would wager that there are a lot of c compilers out there on many
> > different platforms and of many different vintages and that removing
> > that FAQ may be premature.
>
> That seems like a sensible position. Unless a FAQ entry is actually
> incorrect, I don't see any justification in removing it.


Thank you for your opinion.


>
> --
> Michael Wojcik michael.wojcik@xxxxxxxxxxxxxx
>
> However, we maintain that our mission is more than creating high-tech
> amusement--rather, we must endeavor to provide high-tech, high-touch
> entertainment with an emphasis on enkindling human warmth.
> -- "The Ultimate in Entertainment", from the president of video game
> producer Namco

.

Relevant Pages

  • Re: I need a new compiler...
    ... Michael Wojcik wrote: ... comp.lang.c FAQ would also have cleared up this misconception. ... A pointer is a reference to any data element ... The quoted text doesn't say that pointers could be ...
    (comp.lang.cobol)
  • Re: comp.lang.c Answers (Abridged) to Frequently Asked Questions (FAQ)
    ... >> Michael Wojcik wrote: ... >> You didn't see his opinion that it should be removed from the FAQ? ... > library routine that still has that flaw. ... that the issue is no longer applicable to ANY compiler. ...
    (comp.lang.c)
  • Re: comp.lang.javascript FAQ question
    ... Richard Cornford is currently on charge of the group FAQ and why his ... Thusly if Mr.Cornford is in a private opinion ... this forum and the results are by mutual consent (albeit passive ...
    (comp.lang.javascript)
  • Re: Web Server
    ... Now I have looked at the FAQ ... IP and TCP layer or Application Layer too? ... My opinion: Regarding the Product specs & faq: ISS should write exactly ... If they have an ALG for web services they could provide some ...
    (comp.security.firewalls)
  • Re: Web Server
    ... Now I have looked at the FAQ ... IP and TCP layer or Application Layer too? ... My opinion: Regarding the Product specs & faq: ISS should write exactly ... If they have an ALG for web services they could provide some ...
    (comp.security.firewalls)