• To: <xml-dev@l...>
• Subject: Re: Refreshed genx.h, plus some plans
• From: "William J. Kammerer" <wkammerer@n...>
• Date: Sat, 24 Jan 2004 19:58:24 -0500
• Organization: Novannet, LLC. Columbus, US-OH
• References: <200401250024.i0P0O2NK093024@a...>

Ummm...  I don't think you are supposed to ignore those messages that
encourage you to "cast types" in the first place:  it's the C compiler's
way of "enforcing"  const-ness.

William J. Kammerer
Novannet, LLC.
Columbus, US-OH 43221-3859
+1 (614) 487-0320

----- Original Message ----- 
From: "David Tolpin" <dvd@d...>
To: <xml-dev@l...>
Sent: Saturday, 24 January, 2004 07:24 PM
Subject: Re:  Refreshed genx.h, plus some plans


Rich Salz:
> > > BTW, the API doesn't have const-correctness yet.
> >
> > Why is 'const' useful?
>
> Don't you want to know if genx is going to copy the pointers or copy
the
> data pointed to by them?

The sad thing is that no C compiler is able to enforce const-correctness
consistently; they are only good as comments, and as such, I prefer
comments over keywords. This keyword gets in the way and forces to
cast types; it never helps.

• References:
  • Re: Refreshed genx.h, plus some plans
    • From: David Tolpin <dvd@d...>

• Prev by Date: Re: Refreshed genx.h, plus some plans
• Next by Date: Re: Refreshed genx.h, plus some plans
• Previous by thread: Re: Refreshed genx.h, plus some plans
• Next by thread: Re: Refreshed genx.h, plus some plans
• Index(es):
  • Date
  • Thread