Re: [If/then and sequences...]
- Posted by Ben Fosberg <BenFosberg at ATT.NET> Aug 29, 2000
- 416 views
Granted - my question was intended to ask which of the many possible arbitrary ordering schemes Kat was interested in. I suspect this will be a very contentious matter, and that any scheme chosen will, of necessity, only appeal to a minority of users. If the ordering scheme implemented doesn't relate to your use of sequences, then it's just useless weight in the core language. IOW, the "rules employed" are extremely material - make or break. For that reason, I'd say t it's very much the kind of thing that belongs in application code, not the core language. However, I wouldn't fight to keep it out, and one of you sharp guys (the term is meant sincerely) may come up with an ordering rule that _is_ widely applicable and quite useful. Derek Parnell wrote: > It gives us a way of arbitrarily, yet consistently, ordering a set of > sequences. In other words, it enables us to know with 100% accuracy, where a > given sequence is in an ordered set of sequences. The rules employed to > determine which of two sequences comes first is arguably immaterial, as long > as they always work the same way. > > ----- Original Message ----- > From: "Ben Fosberg" <BenFosberg at ATT.NET> > To: <EUPHORIA at LISTSERV.MUOHIO.EDU> > Sent: Wednesday, August 30, 2000 6:12 AM > Subject: Re: [If/then and sequences...] > > > What does it mean to say that one sequence is "greater than" or "less > than" another sequence, > > given that the constituent "elements" of a sequence could be of any data > type, including > > other sequences? > > > > Kat wrote: > > > > > On 29 Aug 2000, at 7:00, Michael Nelson wrote: > > > > > > > David Cuny wrote: > > > > <snip> > > > > > Some people might thing that EE or Win32Lib is my greatest > contribution to > > > > > Euphoria. Not so! It was haraguing Robert into adding equal() to the > > > > > Euphoria. > > > > > > > > David, > > > > > > > > Could you also harrange him into adding greater() and less()? Maybe > > > > not_greater(), not_less() and not_equal() could also be added--but I > see no > > > > real gain over not greaater(), not less() and not equal(). > > > > > > This points out the lack of a couple basic commands we could really use. > I still vote for > > > goto's, especially since i expect to see a lot of them in the translated > C code. > > > > > > Kat