Gilles Detillieux wrote:
> String foo("bar");
> String abc = "xyz";
>
> If they do, aren't we going to get warnings all over the place? If they
> don't, then I'm not clear on what discards the const, and what doesn't.
They don't. We use these all over the place. That's what confuses me
about this one construct. I don't see an explicit const!
> to simply declaring function arguments as char *. The standard is kinda
> confusing too. I'm still not clear on the difference between const
> char *foo and char * const foo, and when to use which. Eventually,
I agree. And since I don't have a good reference that covers the
standard, I can't look it up. (Yes, I could buy the standard, but the
public comment version was rather dry reading.)
As for changing the methods, I agree we eventually need to update them.
In the meantime, we clearly need to get a feel for what's accepted and
what's not! :-)
(And I need to remember where my malloc()s occur...)
--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.