Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

iOS and MacOS / Semantic Issues, Deprecated Issues, etc. in Xcode 5

Author
Message
Braj
8
Years of Service
User Offline
Joined: 21st Feb 2014
Location:
Posted: 27th Feb 2014 20:17
Is there some type of instruction on how to rid or fix these types of issues that occur in Xcode 5 when interpreting your AppGameKit Tier 1 project at the first build/run? I'm not too familiar with Xcode 5 and I'm sure the interpreter causes the same issues to everyone's AppGameKit projects on the first build/run in Xcode.

Thanks!
Ancient Lady
Valued Member
18
Years of Service
User Offline
Joined: 17th Mar 2004
Location: Anchorage, Alaska, USA
Posted: 28th Feb 2014 04:15
Different issues might have different solutions.

What, specifically, are you seeing?

Cheers,
Ancient Lady
AGK Community Tester and AppGameKit Master
Braj
8
Years of Service
User Offline
Joined: 21st Feb 2014
Location:
Posted: 3rd Mar 2014 19:40
Thanks for the reply.

Issues like this occur:

- Conversion from string literal to 'char*' is deprecated
- Comparison between NULL and non-pointer ("int" and NULL)
- "UIAccelerometer' is deprecated
- Unused Variables (DOES THIS ONE MATTER OR NEED TO GET FIXED?)
- Comparison of unsigned expression <0 is always false (DOES THIS ONE NEED TO BE FIXED TOO?)
- Add explicit braces to avoid dangling else (IT STILL WORKS, DOES IT NEED TO BE FIXED UP?)
Ancient Lady
Valued Member
18
Years of Service
User Offline
Joined: 17th Mar 2004
Location: Anchorage, Alaska, USA
Posted: 4th Mar 2014 03:02
What version of AppGameKit are you working with v10821 or v10819?

Quote: "- Conversion from string literal to 'char*' is deprecated"

'deprecated' does not mean it won't work. And, once it is compiled, it doesn't matter.

Quote: "- Comparison between NULL and non-pointer ("int" and NULL)"

Can you show the line of code for this one? It probably doesn't matter.

Quote: "- "UIAccelerometer' is deprecated"

Doesn't really matter, it still works. Apple likes to change things a lot.

Quote: "- Unused Variables (DOES THIS ONE MATTER OR NEED TO GET FIXED?)"

Totally ignorable.

Quote: "- Comparison of unsigned expression <0 is always false (DOES THIS ONE NEED TO BE FIXED TOO?)"

What does the code on this line look like?

Quote: "- Add explicit braces to avoid dangling else (IT STILL WORKS, DOES IT NEED TO BE FIXED UP?) "

I've never seen this message. But I would follow the advice just for neatness sake.

Cheers,
Ancient Lady
AGK Community Tester and AppGameKit Master
Braj
8
Years of Service
User Offline
Joined: 21st Feb 2014
Location:
Posted: 4th Mar 2014 22:47
I'm using ver108.21

Do I have to fix the deprecated and semantic errors or will Apple be fine with them or not see them when I submit?



The line of code for the "Comparison between NULL and non-pointer" error is:

if ( pIncludeFile && strcmp (pIncludeFile, "" )==NULL )

and it happens again:

if (strcmp (g_pInterpreterByteCodeFile, "" )==NULL )



The line of code for the "Comparison of unsigned expression <0 is always false" error is:

if ( dWLatestArrayOffset < 0 || dwLatestArrayOffset >= pdwHeaderDimSize[9] )



Thank you so much for your help!
Ancient Lady
Valued Member
18
Years of Service
User Offline
Joined: 17th Mar 2004
Location: Anchorage, Alaska, USA
Posted: 6th Mar 2014 03:05
Apple won't know about anything that shows up as warnings during the compilation. They only see the finished product.

The two NULL comparisons should be changed just to be safe. I think the NULL should be replaced with 0 (zero).

The last one can simply be ignored.

Cheers,
Ancient Lady
AGK Community Tester and AppGameKit Master
Braj
8
Years of Service
User Offline
Joined: 21st Feb 2014
Location:
Posted: 6th Mar 2014 06:43
Thanks for the reply.

The second NULL was fixed, but the first now says that the line above it is getting a NULL error. The line is:

char pFullErrorText [512];


And also, will ignoring the other Semantic and Deprecations we spoke about have a negative effective on the program? Or are they just notes for me, highlighting things I could change but don't have to?

Thanks for the help thus far!!
Ancient Lady
Valued Member
18
Years of Service
User Offline
Joined: 17th Mar 2004
Location: Anchorage, Alaska, USA
Posted: 8th Mar 2014 02:25
I don't think it should cause any problems.

If you are worried about the semantic issues, edit the file to fix them.

Try posting several lines before and after the one getting the NULL error. (You can put things in code blocks by highlighting the text and then clicking on the 'code' button in the message posting form.)

Cheers,
Ancient Lady
AGK Community Tester and AppGameKit Master
Braj
8
Years of Service
User Offline
Joined: 21st Feb 2014
Location:
Posted: 9th Mar 2014 01:28
Here is where the NULL error occurs (it happens in the second line of the "present runtime error as messagebox" section. Even after changing NULL to 0):

Ancient Lady
Valued Member
18
Years of Service
User Offline
Joined: 17th Mar 2004
Location: Anchorage, Alaska, USA
Posted: 11th Mar 2014 04:38
Well, then I guess replacing the NULL with zero doesn't work.

Leave it as NULL and ignore the 'deprecated' message. It still works.

Cheers,
Ancient Lady
AGK Community Tester and AppGameKit Master
Braj
8
Years of Service
User Offline
Joined: 21st Feb 2014
Location:
Posted: 12th Mar 2014 18:38
Thanks for the help!

Login to post a reply

Server time is: 2022-09-25 21:43:41
Your offset time is: 2022-09-25 21:43:41