Re: Proposal for 'math.e' (2007-08-23)
- Posted by Pete Lomax <petelomax at blueyond?r.c?.uk> Aug 23, 2007
- 708 views
Juergen Luethje wrote: > > This is my current (2007-08-23) proposal for a "math.e" standard > include file, according to the discussion here on EUforum. > > }}} <eucode> > global function find_min (sequence list, integer start) > global function find_max (sequence list, integer start) > global function min (sequence list, integer start) > global function max (sequence list, integer start) > global function lesser (object x1, object x2) > global function greater (object x1, object x2) > </eucode> {{{ I thought we had agreed these should be in a separate file, minmax.e. I do not remember and I cannot find anyone specifically objecting to that, other than CChris once saying he was "not sure" and "not against this split", and in the next post reinventing your "allinc" idea seemed to sway him. I also thought the final outcome of that long discussion was a general agreement that no-one gets to use "min" and "max" to avoid ambiguity. I shall restate my exact position on this: I would not be too miffed if someone nicked the "min" name for a single-parameter function min(sequence list), but once it has two parameters, that is just asking for trouble. I also cannot imagine any, let alone many, cases where the functions min() and max() as posted would be useful, since they return a value not an index and I question what you would do once you've processed that item and how/why would you setup a suitable "start" value?? Regards, Pete