7:49:10jackdanielOK, so I have a consistent solution for the bug identified yesterday
7:49:51jackdanielOR type specifier in CLX in getter only accepts two types and first must be either NULL or (member …), otherwise error is signalled at compilation time
7:50:26jackdanielsimply changing order of checks wouldn't resolve the core issue that getters assume that type is correct
7:51:02jackdanielcheck for NULL and MEMBER may be easily open-coded in OR though without such limitation
7:51:28jackdaniel(not so much more arbitrary types, like resource ids and others - given how it looks in clx code)
8:49:09jackdanielso this is it: https://github.com/sharplispers/clx/pull/125
17:38:40jackdanielscymtym: thanks for looking at the pull request at clx
17:39:39jackdanielI've pushed the fix. fact that it was ,@ was due to the fact forms were collected that way (with a reason) before the change and I didn't think about modifying that.