I have just installed your script and I guess I do not understand the
use case.
The use case is:
class Foo:
def m1(self, a,b): <-- it will create self.a = a, self.b = b
Fabio:
I am pretty uneasy about these tricks to kill undefined symbols. I
don't understand what is going on here, but it seems to work. It looks
too much like magic.
Well, that's just untill I make the scripting environment recognize all those tokens. You could actually create a jython project in your scripts and add all the eclipse jars to it, but I'd rather wait a little and have some check where you could say 'ok, I want to recognize as valid imports all the jars from Eclipse'.
I don't understand why we have to lie on the from lines, or is this
always the case with Jython and Pydev extensions?
As I said, you could configure your project with all that, but it would take to much work to be good for using, so, given some time, I'll make it recognize that.
I don't think that True/False appeared in Python until 2.3 or 2.4 and
Jython is 2.1.
So, what is going on here? Do these scripts already have a bunch of
things defined that is not apparant until they are executed, but the
compiler cannot be told about them?
Actually... sort of... False and True are only 2.3 onwards, but I add 2 tokens: False=0 and True=1 to the globals (in the same way I add the cmd and the editor tokens). That's mostly because I was tired of always having to declare those in the top of a jython script, so, good thing I don't have to do that anymore ;-)
Cheers,
Fabio
