Quoting Ian Lance Taylor <iant@xxxxxxxxxx>:
Derek Atkins <warlord@xxxxxxx> writes:
typedef char* PDFFileName;
typedef const char* PDFFileNameConst;
class Foo
{
public:
// If you change this to PDFFileNameConst then the warning goes away
static int Blah(const PDFFileName name);
};
int do_test()
{
return Foo::Blah("bzz");
}
This is expected behaviour. "const PDFFileName" is not "const char*",
it is "char* const".
I certainly wouldn't call this "expected"..
But with the expanation I at least understand why it's happening.
I guess that means if you typedef there's no way to actually
get the "const char*", which perhaps is a bug in the language definition.
Regardless, it IS annoying.
Ian
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warlord@xxxxxxx PGP key available
