Re: Set all bits to 1 in an array of raw bytes

On Thu, 27 Sep 2007 07:10:07 -0700, "iesvs@xxxxxxx" <iesvs@xxxxxxx>
wrote:

sizeof(char) is 1 by definition, always. Guess you meant 'if CHAR_BIT == 8'

When I code I don't assume that sizeof (char) == 1 and I'll never
assume it.

Let's see now -

In this post, you refuse to accept things the standard says
must be true.

In a previous post, you had no trouble assuming things the
standard says cannot be true.

In a third post, you dismissed the idea that you needed to
learn the basics of the language.

Not really the best approach for obtaining help here. All in all, you
give every appearance of being a troll. Don't be surprised if the
only responses to your messages are ones telling newcomers to the
language what is wrong with your code.


Remove del for email
.

Relevant Pages

  • Re: Are _T() and TEXT() macros equivalent?
    ... by every single application developed in that language for the last 30 ... are not concerned if a char takes 1 byte or 100. ... Go through the standard and list the sections that use char as byte. ... void write ...
    (microsoft.public.vc.mfc)
  • Re: the standard is so strange
    ... char * p1 = xx; ... had fully defined the language. ... there were already different compilers ... You don't necessarily have to read the standard, ...
    (comp.lang.c)
  • Re: Are _T() and TEXT() macros equivalent?
    ... by every single application developed in that language for the last 30 ... Go through the standard and list the sections that use char as byte. ... Another example concerns any function that takes a void* and writes data as ...
    (microsoft.public.vc.mfc)
  • Re: Malcolms new book - Chapter 1 review
    ... The standard says that a char argument to isspaceis illegal. ... Of course these days the assumption that 1 char is 1 character is often ... You are certainly entitled to your opinion that C is an absurd language. ...
    (comp.lang.c)
  • Re: Is C99 the final C? (some suggestions)
    ... > that someone will try compile their stuff on an old compiler. ... > because the ANSI standard obsoleted them, and everyone picked up the ANSI ... fixed by using another language. ... >>are multiplying two expressions of the widest type supported by your ...
    (comp.lang.c)