On Wed, Mar 11, 2009 at 1:26 PM, Pal-Kristian Engstad
<[email protected]> wrote:
> Keyword arguments is a very important feature, especially when dealing
> with low-level code as well as in game-code....
Every feature is very important to someone.
I was initially concerned that keyword arguments would require
overhauling the type checker, but I now see that this is not true;
it's simply that definitions and declarations must agree.
If we then impose the rules:
1. Arguments are partitioned into those with defaults and those without.
2. Keyword args can always be used to specify values for default arguments
3. If *any* keyword arg is used to specify a mandatory parameter, then *all*
mandatory parameters must be given with keyword args
then I think this all works out sensibly. I still don't plan to
implement this now, but perhaps we should implement the def/decl
agreement in anticipation of adding this in the future.
This isn't doable in the current syntax, because PROCLAIM doesn't
provide any way to specify argument types, but we could deal with this
in the new syntax.
Swaroop: what am I forgetting here, if anything?
_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev
