ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> types-sig
types-sig
Re: [Types-sig] Optional static typing and Python interfaces
by Barry A. Warsaw other posts by this author
Nov 25 1998 4:54PM messages near this date
Re: [Types-sig] "Interfaces" Jargon | Re: [Types-sig] "Interfaces" Jargon
> >>>> "BJ" == Bill Janssen <janssen@[...].com> writes:

    BJ>  	1) Add interface descriptions (.pi files) which used a
    BJ>  slightly different syntax in that they allowed some kind of
    BJ>  optional static typing declarations.  These serve as
    BJ>  documentation; no compilers need muck with them.  Work out the
    BJ>  details of the optional static typing syntax at this stage.

    BJ>  	3) Modify the Python parser to allow optional static
    BJ>  typing in the Python code, using the syntax developed in phase
    BJ>  1.  Beef up the cross-checking program developed in phase 2 to
    BJ>  use these type declarations to aid it in type inferencing.

I'm not sure you need to go to #3.  Why not keep the .pi files
separate?  Yes it's more work, but you also don't have to worry about
the "optional" part of "optional static types".  If the program could
run just as well after removing all the .pi files, you're good to go.

-Barry

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved