OpenEuphoria

Re: Include file such as 'compare.e' or 'find.e'

• Posted by CChris <christian.cuvier at agricul?ur?.gouv.fr> Aug 07, 2007
• 572 views

Juergen Luethje wrote:
> 
> Derek Parnell wrote:
> 
> > Salix wrote:
> > > 
> > > CChris wrote:
> > > > 
> > > > As for the min/max names, they were seen by some as ambiguous. The
> > > > current
> names</font></i>
> > > > are more precise; they may be a problem to tose whose mastery of english
> > > > is
> > > > minimal.
> > > 
> > > I don't get this. Why is it ambiguous? Why is not it precise? 
> > 
> > 'greatest' implies that there might be any number of things to test.
> > 'greater' implies that there are only two things to test.
> > 
> > Thus ...
> > 
> >   function greatest( SEQUENCE )
> > 
> > and
> > 
> >   function greater (OBJECT, OBJECT)
> > 
> > But as you say, it is a subtle distinction that only some English speakers
> > might
> > pick up on.
> > 
> > So if we are going to have one signature of 'sequence' and another of
> > 'object,
> > object', how should we name the functions (consistently) to give the reader
> > a mnemonic to tell them apart from each other?
> > 
> > I don't have an answer to that one yet.
> 
> How about
> - find_min(SEQUENCE)
> - find_max(SEQUENCE)
> - min(SEQUENCE)
> - max(SEQUENCE)
> - lesser(OBJECT, OBJECT)
> - greater(OBJECT, OBJECT)
> 
> I think this wouldn't cause confusion.
> 
> Regards,
>    Juergen

That would be better than the current naming scheme.
Note however that compile.e, like any language I know, defines min()/max() as
the two object thing. In maths, you can overload min(); in Eu, you unfortunately
cannot.
And of course adding the bounds() parametrised function as well.

CChris