Comment by briancr

Yes and the simplicity extends to function definitions too, since you don’t have to specify any type info. E.g.

f :: { ; print(args) }

Brevity is especially nice for inline/anonymous functions.

You can definitely use args.num, args.type[], and args.indices[] to figure out which optional parameters were passed, but I’ve decided that it’s usually easier to pass a full set of parameters into C and have the scripted wrapper handle the optional params. This is easy in Cicada because of ‘code substitution’ (one of the innovations I’m proudest of and if you’ve seen this elsewhere please let me know!). Example:

callC :: {

    mandatoryArgs :: { int, int }

    optionalArgs :: { str :: string; str = “default” }

    code

    mandatoryArgs = args

    optionalArgs(), (optionalArgs<<args)()    | set default, then allow user to change it

    $Cfunction(mandatoryArgs, optionalArgs)

}

Then you can call it with or without modifying the optional parameters from their default values.

callC(2, 3) | uses the default string

callC(2, 3; str = “modified param”)

callC() runs its arguments as a function, substituted into the params variable, allowing the arguments to modify params. This is weird and I haven’t seen it elsewhere, but it’s very useful.