Home/ Questions/Q 993063
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T06:21:42+00:00

I find myself casting return types alot to silence compiler warnings and it always

  • 0

I find myself casting return types alot to silence compiler warnings and it always makes me feel like i’m doing something wrong.

This example is Objective-c

const char *strBuf = [anNString UTF8String];
[anOutputStream write:strBufr maxLength:len];

This goves me a compiler warning as
-UTF8String returns const char * and -write:maxLength: takes const uint8_t *

So, knowing no better i would usually add the cast to stop the nagging and carry on my merry way.

Is this bad style (on my part), or just the way it is?

I appreciate any thoughts or advice.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There is no way around this. C, C++, and Objective-C are strongly typed languages. So, anytime there’s a type conversion like that, you’re going to get a compiler warning. The only way around it is to use the same types which is not always possible. It’s typical. I would keep doing what you’re doing. Don’t ignore the warnings or turn them off because there will be one type conversion that will be an error that you will want to fix. If you turn of the warnings, you’re leaving yourself vulnerable to getting a bug that will be very hard to find.

    • 0