So there will be no objection
 if I removed translator_proto-KEES.py and translator_proto-KLUEV.py in my 
next commit then?

will leave translator_dict.py as is.

Sarvi

On Monday, October 28, 2013 11:11:20 PM UTC-7, Kees Bos wrote:
>
> On Mon, 2013-10-28 at 22:17 -0700, Sarvi Shanmugham wrote: 
> > I see 4 different translator options 
> > translator_dict.py 
>
> That's a start of a translator that stores attributes/methods in a dict. 
> Is thus by design way more pythonic and slower (always calls getattr) 
> than the default translator. It's not finished. 
> > 
> > translator_proto-KEES.py 
> > translator_proto-KLUEV.py 
>
> These are remnants of a merge conflict. The KLUEV version might have 
> support for runtime compilation. I'm not sure, but that is what he was 
> working on. As far as I'm concerned, both can be removed. 
> > 
> > translator_proto.py (default I think) 
>
> Yep. That's the default. Classes are based on javascript prototyping. 
> > 
> > 
> > Does any know what the difference between them is or why there are so 
> > many? 
> > Is this something that can be coalesced? 
>
> See above. 
>
>
>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Pyjs.org Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to