SAMP MType parameters issue
boch at newb6.u-strasbg.fr
Thu Nov 6 05:33:30 PST 2008
> As a rule I'm not in favour of letting the standard be too much
> influenced by language-specific considerations. However, using the
> python named parameter syntax for MType parameters seems like such
> a good match that I think it would be nice to facilitate this.
> Similar considerations might apply for other languages with similar
> syntax as well (though I can't think of any off hand).
> Although this does constitute a change to existing practice, as yet
> no applications are in public release, so changing it now is not going
> to present much difficulty.
> So, my vote is in favour of changing these parameter names as Luigi
> suggests, and introducing at least a RECOMMENDation (or should it be
> a REQUIREment?) in the standard that future MTypes use parameter
> and (for symmetry) return value names following the suggested BNF.
While, as Mark, I don't like much changes in standards being dictated by
some implementation specific details, I would support this change as
long as we decide it quickly, before any of our SAMPified applications
become publically available.
More information about the apps-samp