Compiler standards medley

PLCnext Engineer
1

I finally realize that compiling with the provided toolchain (arm-pxc-linux-gnueabi-g++) with success do not mean there is no problem in the code. Some parallel compiler process in Eclipse still finds more problem and display them as hint in into the editor. Is there any configuration setting I am missing that could unify the behavior ? Also, I must point out that using VisualC++ pointed out obvious error like using the keyword “and” (pascal) instead of “&&” (C++). May be you defined some aliases… That lead to another question about using VC++ vs Eclipse: What is the best choice for now and the future of your platform ? Thanks

2

Hello Fblanchard, Yes just compiling successfully doesnt mean that there are no logical mistakes.

Its always possible to create Segmentationfaults ect… But what you describe is something like this? So you succesfully compiled something like this:

bool test = false;  
>  bool test2 = false;  
>  bool test3 = test and test2;

And that caused your controller to crash?

bool test = true;  
> bool test2 = true;  
> bool test3 = test and test2;  
> if(test3)  
> {  
>  log.Info("ow truee");  
> }

this works fine for me…

23.03.18 12:38:04.863 BPLibrary.BPComponent.BPProgram INFO - ow truee  
> 23.03.18 12:38:04.963 BPLibrary.BPComponent.BPProgram INFO - ow truee  
> 23.03.18 12:38:05.063 BPLibrary.BPComponent.BPProgram INFO - ow truee  
> 23.03.18 12:38:05.163 BPLibrary.BPComponent.BPProgram INFO - ow truee

At the End of this year there will be a new Plugin/toolchain in the form of a CLI.
And additional a Eclipse and VS Plugin will be provided.
With the CLI it is basically possible to include it in any IDE. Additional to the C++ Plugin: Next months a VisualStudio 2015 Plugin will be released that provides the possibility to programm C# functionblocks and functions for IEC.

3

My first question was not clear. It is not about logical mistakes, but syntaxial mistakes. After a completely succesful build using the arm-pxc-linux-gnueabi-g++ toolchain, the Eclipse environment will put some red markers on perfectly justifiable syntaxial errors (like undefined types caused by a missing include). But now, I am just fearing that this is just a side effect of something else. Next time I fall into this kind of problem, I will attach a code code snippet. Thanks.

4

hey, checkout this FAQ:

Error AddPortInfo FAQ is that the error that was highlighted?

5

You are right. I just enabled this “PLCnext Language Settings Provider” setting and the AddPortInfo() are not underlined red anymore. I hope this will help for the other problem I had. I will keep you in touch. Thanks.