Reference thread:
www.b4x.com
In a project I had a code module called base, which worked fine. But then I added some b4xlibs that also (unknown to me) held variables with this exact name. So the compiler didn't know which base was referred to during compilation, which caused a very strange and difficult-to-understand crash message.
It seems possible to stop compilation when there is a name ambiguity and inform the user about the issue.
BBCodeView crashes in Debug, works fine in Release
I have a project in B4J that contains a layout with a BBCodeView. I wanted that layout in another B4J project, so I made a new layout in the new project and did the copy/paste thing from the old project using the Designer. The first project (that I copied from) works just fine in debug and...
www.b4x.com
In a project I had a code module called base, which worked fine. But then I added some b4xlibs that also (unknown to me) held variables with this exact name. So the compiler didn't know which base was referred to during compilation, which caused a very strange and difficult-to-understand crash message.
It seems possible to stop compilation when there is a name ambiguity and inform the user about the issue.
