Re: CW10 assignment, void*, func ptr warnings...
- From: "hp" <harry@xxxxxxxxx>
- Date: 15 Nov 2005 08:59:23 -0800
> > Starting my CW9.4 to CW10 migration. So far I am unsuccessful in
> > compiling the simplest of projects. Sigh.
>
>
<snip>
> Just my personal opinion here, but wish it had never worked. LOL
> Nesting statements like this saves a line or two of code, but makes
> code harder to read in the process. I'd just have:
>
understand. Things like this happen when I get lazy. The relational
expr initially only used strlen(), then a later modification to the
block required the value, so to avoid another call to strlen() the
assignment gets created.
> In any case, your code compiles just fine in my application, so I don't
> know why you're getting a warning.
>
Perhaps there is a pragma for this? I hate to do that, cuz the warning
has saved me before; How about this Ron? Howard?
> > 2) Warning : illegal explicit conversion from 'bool (*)(bool)' to 'void
> > *'
<snip>
> >
This is another warning that is "in the way". I like "clean" builds ...
that way one can be confident the the whole build process is not
introducing new issues...
> > 3) errors about func signatures; eg, when calling NewUserItemUPP(), I
> > get errors about the func ptr:
> >
> > Error : function call 'NewUserItemUPP({lval} pascal void
> > (OpaqueDialogPtr *, short))' does not match
> > 'NewUserItemUPP(pascal extern "C" void (*)(OpaqueDialogPtr *, short))'
> >
> > Must I now declare them with extern "C" ??
> >
> > Gee. These kinds of issues are really not helpful when one has real
> > problems to solve..
>
> I don't know why the extern "C" part is in there. I don't see this when
> I use UPPs. The following compiles just fine for me:
>
Again ... can anyone at Metrowerks/FreeWerks comment on this?
This is preventing me from getting anything running; Maybe regressiing
to CW9.5 is the right answer...
>
> Out of curiosity, do you really need to stick with the Dialog Manager?
>
Nope. There are just bigger fish to fry...
When a day is 48hrs long, there might be hope of getting caught up.
-harry
.
- References:
- Prev by Date: CodeWarrior 10.1 for Intel/Rosetta Debugging?
- Next by Date: How to loose customers--the 10 step registration
- Previous by thread: Re: CW10 assignment, void*, func ptr warnings...
- Next by thread: CodeWarrior 10.1 for Intel/Rosetta Debugging?
- Index(es):
Relevant Pages
|
