[Swift-devel] Call function.

[Michael Wilde]

I vote for 1.

- Mike


----- Original Message -----
> From: "Ben Clifford" <benc at hawaga.org.uk>
> To: "Mihael Hategan" <hategan at mcs.anl.gov>
> Cc: "swift-devel Devel" <swift-devel at ci.uchicago.edu>
> Sent: Tuesday, August 16, 2011 7:55:59 AM
> Subject: Re: [Swift-devel] Call function.
> On Aug 15, 2011, at 6:47 PM, Mihael Hategan wrote:
> 
> >>
> >> 1. Keep them in the same namespace, treat all procs as if they were
> >> equivalent to name = signature {body}. Disallow variables and
> >> procedures
> >> with the same name.
> >> 2. Do not keep them in the same namespace and consider the
> >> namespace
> >> implicit in the type. So if I assign to a non-procedure type then
> >> it's a
> >> normal variable, and if I assign to (or use in the context of) a
> >> procedure type, then it's a procedure. This could be confusing to a
> >> user
> >> and it requires one to look at the context of an expression to
> >> determine
> >> its type, which complicates the compiler code.
> >> 3. Have some special keyword that indicates the procedure
> >> namespace:
> >> myfn= proc f (or myfn = proc(f) or myfn = proc:f).
> >>
> >
> > Ok, so let's make this democratic. Opinions, preferences?
> 
> 
> I prefer something like 1. 3 is ok - I think its unnecessary
> keywordage but fine otherwise. not 2.
> 
> --
> 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel

-- 
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory