Re: [Jython-dev] Shrinking PyObject.call(PyObject one, PyObject two, etc...) when 1.5 is the ba

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

On Fri, 08 Dec 2006 10:15:33 -0500, Leo User <leo...@ya...> wrote:

> with varargs being a feature in Java 5, would it not
> make sense to replace all of these with one "__call__"
> method:
> public PyObject __call__(PyObject ... args)
>
> Maybe there will be other candidates for shrinking,
> this one stuck out. :)
>
> what say you?
> leouser

I'm not a Jython dev, but I say if isn't broke, there's nothing to fix.   
It makes sense to phase Java 5 features in, but I wouldn't expect to see a  
rewrite just for the sake of a rewrite.

-- 
Kevin Menard
Servprise International
WebReboot -- Remote Reboot Without Pulling the Plug
800.832.3823

Re: [Jython-dev] Shrinking PyObject.__call__(PyObject one, PyObject two, etc...) when 1.5 is the ba

Re: [Jython-dev] Shrinking PyObject.__call__(PyObject one, PyObject two, etc...) when 1.5 is the baseline?

Re: [Jython-dev] Shrinking PyObject.call(PyObject one, PyObject two, etc...) when 1.5 is the ba

Re: [Jython-dev] Shrinking PyObject.call(PyObject one, PyObject two, etc...) when 1.5 is the baseline?