Hi Kyle,
On 07/13/12 05:38 pm, zmafoox wrote:
The new initialization code works more consistently. Long ago (prior to
June 2007) the controlling expression in a conditional could be anything
and follows the C rules -- 0 meant FALSE, anything else was TRUE. Folks
requested that I return to the original JAL behavior which required the
controlling expression to be a BIT.
That is probably before the time I got involved with JalV2.
Would anyone be offended if the new compiler causes
warnings in the existing samples? There are ~50 cases of this.
Difficult to say for sure, but I can hardly believe anyone would
protest. Hopefully most of these cases are in generated examples. That
would reduce the amount of work. Anyway it won't be a difficult job once
you provide a new (beta) compiler.
Regards, Rob.
--
R. Hamerling, Netherlands --- http://www.robh.nl
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en.
