Large compiler refactoring

[Erel]

Just finished a large refactoring related to the way variables and parameters are handled internally. Zero effect on B4X code behavior, but will make it easier to introduce new features. More to come...

 

[Peter Simpson]

Excellent news @Erel , thank you...

 

[mcqueccu]

Just finished a large refactoring related to the way variables and parameters are handled internally. Zero effect on B4X code behavior, but will make it easier to introduce new features. More to come...

We can't wait....

 

[virpalacios]

Just Great News as Always

 

[Erel]

 

[Alessandro71]

Default parameters?

 

[Erel]

Yes. Optional parameters.

 

[Daestrum]

Optional as needed on definition, not needed on call?

 

[LucaMs]

View attachment 173107

17
What did I win?


I'm really looking forward to seeing what other great new things like this there will be.

A naughty question: will CallSub and CallSubDelayed also be able to call Subs that have optional parameters?

 

[byz]

The anticipated reform. Does it imply that the intelligent evolution of the b4x ecosystem can be controlled through parameterization.

 

[Erel]

Optional as needed on definition, not needed on call?

Yes.

naughty question: will CallSub and CallSubDelayed also be able to call Subs that have optional parameters?

No. Optional parameters are set during compilation so dynamic calls must include all parameters.

 

[Erel]

Boring:

Dim b() As Byte = "aaaa".GetBytes("UTF-8")
'''
Dim s As String = BytesToString(b, 0, b.Length, "UTF-8")

Not boring:

Dim b() As Byte = "aaaa".GetBytes
'''
Dim s As String = BytesToString(b)

 

[Alessandro71]

does this also means that it will be possible to call "Initialize" on a generic "Object" by using CallSub without knowing it's actual Class?

 

[Erel]

No. It has nothing to do with it. You should create a Factory class that instantiates new objects based on some parameter. More information in a new thread.

 

[Alexander Stolte]

Optional parameters

 

[Erel]

At last we can get rid of the unused "job name" parameter (it was important before the Wait For feature was implemented):

Dim j As HttpJob
j.Initialize 'instead of j.Initialize("", Me)
j.Download(url)

Public Sub Initialize (Name As String = "", TargetModule As Object = Me)

 

[Alessandro71]

Public Sub Initialize (Name As String = "", TargetModule As Object = Me)

so "Me" will be evaluated at run-time, not at compile time, like the "Name" parameter
"Me" will be set to the calling object not the object containing the Initialize sub.
is it a special case or it will be applied to all parameters?

 

[Erel]

The default values are set during compilation, not runtime.

"Me" will be set to the calling object not the object containing the Initialize sub.

True.

is it a special case or it will be applied to all parameters?

It is not a special case, though I assume that most default values will be of constant values.

 

[Alessandro71]

The default values are set during compilation, not runtime.

it stills puzzles me, since actual Me values is unknown at compile time, but i'm fully confident about your work

 

[Erel]

'class method
Public Sub Example(x As Object = Me, y As Int = 4)

'calling:
Object1.Example
'compiler completes it as if the code is:
Object1.Example(Me, 4)