A procedure may contain a /* without a matching */. The result is that the balance of the procedure after the /* is commented out (without any indication to the user). I don’t really have a problem with this but I do find this odd:
This code"
local a
message "hello Jim"
/*
not a statement
compiles and runs. This:
local a
;message "hello Jim"
/*
not a statement
causes a “syntax error” message but this doesn’t:
local a
;message "hello Jim"
a = str(6)
/*
not a statement
I wonder if this is perhaps a pointer to something not quite right somewhere? Or perhaps, it’s a way of saying, “don’t write stupid code”.