Forums

So it's agreed then, in order:

1) Static methods
2) Method overloading
3) Parameterised constructors



As well as a long list of smaller wishes: the ability to "sendMsg" on a primitive, for properties for controls added in the painter to be protected instead of public, for "protected" to be instances based and not class based.

for "protected" to be instances based and not class based.

I don't understand this one

for "protected" to be instances based and not class based.

I don't understand this one

I have a property on a class which is protected. I should not be able to access this protected property on instance1 of the class when running in a method on instance2 of the class. A protected propery should only be able to be accessed from a method *running on the instance that holds the property*. The way this works in JADE is that you can access the property from any instance of that class, not just the self instance. I consider this to be a bug in the way access modes have been implemented. The same problem exists with protected methods. A protected method should only be able to be called from within another method running on the same instance.

Interesting point allistar.

Just to muddy the waters even more, maybe off topic, and I guess one could go on and on about features that we'd like but...

Regarding something I tried quite a while back, and on an older Jade version, so correct me if I'm talking nonsense...

I don't think it's possible to specify attributes when defining an Interface, nor (therefore) define a MemberKeyDictionary class with membership ISomeInterface? Only methods?

Interesting point allistar.

Just to muddy the waters even more, maybe off topic, and I guess one could go on and on about features that we'd like but...

Regarding something I tried quite a while back, and on an older Jade version, so correct me if I'm talking nonsense...

I don't think it's possible to specify attributes when defining an Interface, nor (therefore) define a MemberKeyDictionary class with membership ISomeInterface? Only methods?

Déjà vu : https://forums.jadeworld.com/viewtopic.php?f=7&t=2049

I have a property on a class which is protected. I should not be able to access this protected property on instance1 of the class when running in a method on instance2 of the class. A protected propery should only be able to be accessed from a method *running on the instance that holds the property*. The way this works in JADE is that you can access the property from any instance of that class, not just the self instance. I consider this to be a bug in the way access modes have been implemented. The same problem exists with protected methods. A protected method should only be able to be called from within another method running on the same instance.

Wow, I've never tried that - I agree that's not right

Just to close the loop, Class Methods made the cut for the 2016 release.

Class Methods
Benefit
Class methods allow a cleaner implementation of
programming models. Most modern languages provide
this capability and it has been a long requested feature
for JADE.
Description
We will implement Class methods which allow developers
to define and call methods on Classes, without having to
instantiate a dummy object. This will simplify aspects of
development in JADE.

see https://www.jadeworld.com/pdf/tech/JADE_Roadmap.pdf

That's fantastic! I hope we will be able to treat them like normal methods (e.g. call them on instances of the class as well as the class itself, and do the equivalent of "sendMsg" on them). I look forward to upgrading (probably later next year) to get this feature.