RE: [Jython-dev] Jython and native java merged with simplicity

[Garcia, M. <mg...@Bu...>]

I'm confused about this topic you guys are discussing.  Can you please
elaborate as to what benefits this would have or what purpose this will
serve?

thanks,
Mick 

-----Original Message-----
From: john coppola
To: Samuele Pedroni
Cc: jyt...@li...
Sent: 8/7/01 9:56 PM
Subject: Re: [Jython-dev] Jython and native java merged with simplicity

thanks for the encouraging remarks!

these dev discussions have been really good.

lots of thinking going on...


I already have something preliminary whipped up.
And it is pretty simple like I though it would be.  As
expected the ghosting does not slow the interpreter
down since the method calls on the java skeleton are
fast.

Now the real speed up will be when I do benchmarking
of algorithms done in python against the same
algorithms implemented in the ghost class on ghost
attributes.


> Why this two-places approach? once you have a
> skeleton
> you can store things there, unless an attribute
> is not a pre-existent java field.

Your right!  No duplication at all.  A bit of tweaking
to dir function and __dict__.keys() things like that.
Doesn't look like this will break anything!


So far I haven't needed to use reflection.  I don't
think I will, since that step has already been done
for me by way of the interpreter.

The way that I am doing it now, for each attribute foo
in the skeleton class, one must define accessor
methods set_foo and get_foo.  Perhaps this is
cumbersome.


-john


__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/

_______________________________________________
Jython-dev mailing list
Jyt...@li...
http://lists.sourceforge.net/lists/listinfo/jython-dev