Re: Re: pyrex like compiler

Mark Hahn <[email protected]>:

> Greg: What is the Pyrex licensing situation?

Pyrex is released under the you-don't-need-a-license license.
In other words you're welcome to do whatever you want with it.
Feel free to hack it into a Prothon version if you like.

> I assume the current Pyrex code is wrapped around Python objects and
> stack, so we would need to rewrite it for Prothon, correct?

Yes.

> Is Pyrex capable of wrapping C and C++ libraries?

Currently it only interfaces with C, but that's only because I haven't
gotten around to providing any C++ support yet.  There's nothing
preventing it in principle.

> Paul Prescod:
> The Python syntax (and semantics) of Pyrex is the whole point. After all,
> Python programmers like programming in Python and often dislike C. Prothon
> programmers will like programming in Prothon and will often dislike C.

That's more or less the reasoning that led me to use Python syntax for
Pyrex. I started out wanting something that would let me write
functions with Python headers and C bodies. The main syntax was going
to be C, with extensions for dealing with Python types. 

But when I got to the point where I realised I would need to add a
try-except statement for handling Python exceptions, it suddenly
occurred to me that there's already a well-known language that has
everything necessary for handling Python things, and it's called
Python!

That's when my thinking flipped over, and I decided to use Python as
the main syntax, with extensions for C types. I think it turned out to
be a good choice.

Greg Ewing, Computer Science Dept, +--------------------------------------+
University of Canterbury,	   | A citizen of NewZealandCorp, a	  |
Christchurch, New Zealand	   | wholly-owned subsidiary of USA Inc.  |
[email protected]	   +--------------------------------------+