SDK 4.1.6 generating new errors and warnings ??

With 4.1.6, type checking in on by default.  It wasn't with 4.1.5.  You may want to try with type checking off, With VS Code, it's an extension setting here:  I have default selected, another option is off..

Thanks for your quick reply Jim.

I'm using Eclipse. I've looked for compiler options in Preferences | Connect IQ | Compiler and don't see anything that would allow me to enable / disable compiler options. Is there some other place where I can change compiler options in Eclipse ?

And, does type checking explain the "could not find method" and "cannot find symbol" errors ?

For command line options, put in -l 0

and - O3 to switch optimise on

project.typecheck = 0
project.optimization = 2

Or you can just do it on a per project basis with 4.1.6 and add this to your project's monkey jungle:  Set the type checking and optimization level

Thanks to both of you.

The -l 0 got me past the errors and warnings.

I do want to experiment with the optimization.

Is there documentation somewhere that describes the command line options ?

The same question applies for putting compiler options in the monkey jungle.

I've done some hunting and so far have not found that. 

Can you point me in the right direction ?

A related question - 

Is optimization dependent on type checking ?

Another way to ask that is.... does adding type checking improve optimization ?

I don't know :) I use no type checking but optimisation yes due to:

0. Types does nothing it is only checking during compilation and you have to write a lot additional code. 

1. On some devices I'm near of limit and have a lot of settings so saving 2kb is important.

2. Finally code looks normal!!! You can use const, enum without memory consumption.

And.... is there documentation describing the details of type checking ?

I'm getting "could not find method" errors where the method function referred to is defined in the same source and above the place where it's used in a method(:functionName) call.

Don't know, don't' use :)

Runtime or compiling error?

And after one few days no any problem with -O3.