YesIs this a design decision
Nois there a relationship with obfuscation?
I thinkit is a crude(ish) way to avoid event Subs showing as unused because they are not called from within the app code but from the app's message loop.
No it's not.(it could be a bug)
So I have to assume that you participate in the development of Anywhere Software tools, right?No it's not.
It could be, given that...So I have to assume that you participate in the development of Anywhere Software tools, right?
I helped Erel in the initial development of B4A as I was a significant contributor to its predecessor Basi4ppc. I was the first (as far as I know) to run the initial versions of B4A to identify bugs and feedback to Erel. I wrote many of the initial libraries, some of which, like Reflection and ByteConverter are now part of the B4A standard libraries and some, like Threading, while important initially are less so now that Erel has written asynchronicity into other libraries that most benefit from it.So I have to assume that you participate in the development of Anywhere Software tools, right?
Hi Andy,
I've uploaded a new version of the IDE and the java projects.
Most of the issues we discussed should be fixed.
There are many small improvements.
[technical stuff omitted/]
I'd be happy to hear your comments if you like to play with it. It is located under /beta/b4a.zip.
Regards,
Erel
All this does not convince me but I have to adaptAgraham answer is exact. I voted it up.
The compiler cannot know which subs are "events subs" and relies on the convention that such subs have an underscore in their name.
Glad to know about itI helped Erel in the initial development of B4A as I was a significant contributor to its predecessor Basi4ppc. I was the first (as far as I know) to run the initial versions of B4A to identify bugs and feedback to Erel. I wrote many of the initial libraries, some of which, like Reflection and ByteConverter are now part of the B4A standard libraries and some, like Threading, while important initially are less so now that Erel has written asynchronicity into other libraries that most benefit from it.
From one of our interchanges in 2010 during the development of B4A prior to release.
However, if the name of one of my routines that I will not actually use anymore (old version of my source) contains an underscore, the warning will not happen and my source will be less "clean".
The compiler cannot know which subs are "events subs" and relies on the convention that such subs have an underscore in their name.
And that too should be in Italian, not English, syntax. I agree.2 - the only existing programming language should be B4X.
Is that a bad thing? Underscores are kind of ugly outside of C where everything is lowercased.otherwise I am forced to avoid underscores in Subs that are not events.
I never use underscores in the names of my routines; I did it today and it is precisely for this reason that I realized this only today (in a simple test project).Is that a bad thing? Underscores are kind of ugly outside of C where everything is lowercased.