On 9/20/07, skaller <[EMAIL PROTECTED]> wrote:
> > Someday. I'm doing a bit of work on those os wrappers, and it'd really
> > simplify the interface :)
>
> The main issue is that a given function would have a SET of type
> signatures.
>
> I think overload resolution could handle that easily: instead of
>
>         T1 -> f1
>         T2 -> f2
>
> and match the LHS sig to find the RHS fun to use, just allow
> more entries:
>
>         T11 -> f1
>         T12 -> f2
>         ...
>
>
> Now, actually I lied about 2^N: if we follow the C++/tuple technology,
> then N defaults only makes N+1 functions (all args, the last one
> cut off, the last 2 cut off, etc ..).
>
> Only interesting case then is an array of 20,000 zeros with
> the initial elements specified .. :)

Thats true, but I always hated that about c++. You have to call
functions with such a huge list of temp variables which just make no
sense without referring to some api document. You've dealt with win32,
you know what I mean :)

Plus, if it doesn't automatically generate those intermediary helper
functions, it's just a pain having to do the "f (a:int) => f (a, 1,
2)", "f (a:int, b:int) => f (a, b, 2)", "f(a:int, b:int, c:int) =
{...}", and be a maintenance nightmare if you ever have to propagate
changes to the defaults.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Felix-language mailing list
Felix-language@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/felix-language

Reply via email to