tisis2
tisis2
same issue here
actually it might affect more than just the diagnostic configuration. as we have already seen we have different behavior during runtime, like short circuitng on boolean expressions... and also keywords...
how would the user be able to recognize which error codes are configurable and which are not? it feels strange for me when there is no recognizable difference for the...
maybe something like that... we could also reflect it in the error id and differ between CRIT... and E... for example. but to be honest, i think currently all this...
IEC61131-3 6.6.2.5.3 see the tables e.g. for LREAL_TO_DWORD its defined that it is a binary transfer of the bits on the right side
you are right i think i mixed it up with other conversions
in my understanding i would just treat a ```RETURN 0;``` as a shorthand for ```xxx := 0; RETURN;``` that said... why shouldn't you mix it...
standard perspective: the standard (IEC 61131-3:2013) mentions in 7.3.3.2.1 that comparisons are allowed on same types and if one value is implicit convertable into another in general as @ghaith mentioned,...
also see https://github.com/PLC-lang/rusty/pull/1468 it seems the wrong value you see could be caused by the same this pullrequest targeted
are you sure you running the current source when debugging? it seems very strange that e.g. a tick and t1 are shown as members of PLC_PRG but they are not...