Ghaith Hachem

Knowing that the `UINT` is resolving as `BOOL` kind of explains why there's an undefined `IS_VALID_BCD__BOOL` although I still didn't find the place where we used a `IS_VALID_BCD` on a...

> Hello, I tried to use the `-c` compiling flag to output an object file from a file called `test.st`, and `plc` produced that `bistable.st.o`, idk why. The whole command...

> > Knowing that the `UINT` is resolving as `BOOL` kind of explains why there's an undefined `IS_VALID_BCD__BOOL` although I still didn't find the place where we used a `IS_VALID_BCD`...

I would vote to add validators in that case. I'm not sure why we had the ANY_BIT include BOOL maybe it's part of the Norm, but i'll have to look....

They are redundant, but not "Not allowed" so if a pre-existing project already has such call signatures, we could for example still support it with a warning. I would say...

So the way I've been thinking of this is to add lints which could be configured. This is in progress in #826 . The order will always be an issue...

The function UINT_TO_STRING is not yet implemented in the standard functions, but the signature here is wrong, and therefore you get an error, the signature should be ``` FUNCTION UINT_TO_STRING...

He sorry for the late reply on this, we don't currently support function pointers no. You can always use a Function_Block pointer as a parameter, but this won't allow you...

@zeehans They are not currently planned, but mainly because we can't see a clear usecase where classes/interfaces would not fit here. Our main issue is how do we use it:...

> @ghaith I agree that interfaces handle pretty much the same use case and function pointers would only help developers who prefer not to use OOP. I can only speak...