[pypy-dev] CLI code generation

holger krekel hpk at trillke.net
Mon Mar 20 22:38:00 CET 2006

Hi Anto, 

On Mon, Mar 20, 2006 at 22:29 +0100, Antonio Cuni wrote:
> Niklaus Haldimann wrote:
> >I'm the guy who's working a bit on the Smalltalk backend at the moment.
> >I'm very interested to see how your CLI backend progresses! Ideally, all
> >high-level backends (those based on the ootypesystem) should be able to
> >share some code and concepts. I haven't yet put much thought into this
> >while working on gensqueak, though. But if you see ways to share some
> >abstractions between gencli and gensqueak, you're very welcome to share
> >your ideas or refactor code. I will also watch what you are doing to
> >look for opportunities to unify things.
> I agree, it would be nice to share code, so that it could be reused for 
> future backends, too.
> I have already taken a look to gensquak (it was my starting-point for 
> writing gencil), but I haven't studied it in deep, also because I don't 
> know smalltalk, so it is not easy to follow the code.
> I will check in my work as soon as I have a svn account, so that you 
> will be able to take a look on it.

i sent you mail separately about your new account. 

> A question about the coding rules: must the translator package be 
> written in rpython? I've seen a lot of yield statements, so I think it's 
> not the case: why?

Basically only things that are represented a eventual runtime need to adhere
to RPython restrictions.  In fact, much of PyPy's codebase is not RPython
at all - it's even Anti-RPython as if to make up for having to follow 
more restricted rules somewhere else :)


More information about the Pypy-dev mailing list