[Types-sig] type declaration syntax

[skaller]

Greg Stein wrote:

> >       Viperc _will_ use a global inferencer.
> > Please don't assume "python" means CPython. There are two other
> > full scale implementations now. There may be more in the future.
> > And there may be other programs -- not full interpreters or
> > compilers, like PyLint -- which will _use_ the information.
> 
> But I am talking about CPython. Do what you want with Viper, but I'm
> concerned with the core/authoritative distribution. I do not believe that
> will have a global inferencer. Sure, maybe it will one day, but my
> proposal assumes "no".

	It is possible that Viperc will generate C code for CPython.
In fact, it seems likely. It may be a third part tool, written in
ocaml rather than C, and so not part of the 'core' distribution,
but is a LOT more likely to work than anything that will ever
make it into the core distribution for the simple reasons
that it is written in a language suitable for the task,
unlike C, and it is already under development.

	In fact, IMHO, even Java is a LOT more suitable
for doing this than C will ever be. Perhaps a C version
can be written AFTER a proof of principle version is got working
in a high level language.

	Now, I'd love to be proven wrong, and find a 
real Python compiler in the next major distribution,
so my Interscript program actually becomes useful.
But I'm not going to hold my breath, and I guess that the
'small change left over from DARPA funding' Guido mentions
will not fund a compiler -- indeed, I doubt the WHOLE
of the funding provided would be enough, if it is going
to be written in C.

-- 
John Skaller, mailto:skaller@maxtal.com.au
10/1 Toxteth Rd Glebe NSW 2037 Australia
homepage: http://www.maxtal.com.au/~skaller
voice: 61-2-9660-0850