Constants

Currently there is no built in support for constants.

I do it like this :


then reference someconst anywhere as you would if we did have constant declarations like this :


You can declare the "constant" as any regular B4A type.

Does this make sense?

regards, Ricky

You may declare a special Type called Constants and add multiple items to it.

I use it for Enums but it basically does the same.

Sent from my HTC Desire using Tapatalk 2

Constants are 0-ary functions!

Use something like this to prevent setting the "variable" to a new value:

@Erel:
What's about automagically pre-compiling
to
in the next(?) version of B4A?

What's about automagically pre-compiling...

Click to expand...

There are simpler and (much) quicker implementations.

@Erel: Of course, when you introduce static final vars from Java...

I get frequently frustrated with the lack of constants and enum types. I come from Delphi background where these are used frequently.

I found a way that is helping me with the version 2.50+ when compiling to library option. I create the main class code module, and add another code module only to define in process_globals the constant variables, with 'c' starting on the name.

I name this module with 'const' added to library name, to make more readable.

For those that like creating subs for constants it could be an option also. Since commonly constants are global to the entire source code in almost all languages.

So it will show up even if you do not have the main class created yet.

just my 2 cents.

+1. In 35 years of programming I have never come across a language without constants. Even 8 bit 8080 assembler had it. Utterly essential, especially working across multiple shared modules. Consts need to be public/private too.

Joe_L said:

+1. In 35 years of programming I have never come across a language without constants. Even 8 bit 8080 assembler had it. Utterly essential, especially working across multiple shared modules. Consts need to be public/private too.

Click to expand...

yes, but consider that b4a is new, i believe 2 years old, and there are many things to implement. When i get first version 1.90, was a lot more simple, now we have got some stuff (classes, libraries) I believe we should keep feeding that can help direct where b4a should go.