Re: BeOS PPC Compilation Fixes
On Sun, Dec 03, 2000 at 01:57:44AM -0800, Greg Stein wrote:
> > > Now that is just a dumb compiler if it is complaining about those. "char *"
> > > can legally be passed to a "const char *" function. The other possibility is
> > > that it doesn't think that "char foo" is compatible with "char *foo" --
> > > again, a big problem with the compiler.
> > >
> > > [ I believe both of those issues are consider "standard C" and we shouldn't
> > > "have" to cast. ]
> > >
> > > Which of the two problems is the compiler talking about? const or  ?
> > The problem is with the const. I couldn't find anything about the
> > standard either way in a quick Google search.
> Urk. That is really bad. I'm surprised you aren't seeing more widespread
> problems. The rule is pretty simple:
> void foo(const char *bar)
> You can pass a "const char *baz" or a "char *baz" to the above function.
> Both values are "char *" and the function says "I won't modify it."
> We aren't in a position to retrofit the whole codebase to insert casts to
> include "const" to compensate for a poor compiler. All of those casts would
> end up hiding a typing bug at some point in the future (which is why I hate
Ok, take back everything I said about this. It should work without
those changes. I was just overzealous in adding casts to the calls to
that function. Ignore this patch.
/me votes -1 on /me. :-0
Received on Sat Oct 21 14:36:16 2006
- application/pgp-signature attachment: stored
This is an archived mail posted to the Subversion Dev