Ralf Hemmecke <r...@hemmecke.de> writes: | This is somehow related to | http://groups.google.com/group/fricas-devel/msg/d2befd705391861f | | While looking at jet.spad.pamphlet, I saw something like this. | | until empty? LD1 repeat | ... | | https://github.com/hemmecke/fricas/blob/master/src/algebra/jet.spad.pamphlet#L1085 | | The Axiom Book doesn't mention "until" as a keyword. Aldor also | doesn't have "until". | | In fact, the way it is used, it is just an abbreviation for "while not". | | In order to keep the language as simple as possible, I strongly vote | for removing the "until" keyword. | | Opinions?
To the extent that users will complain about incompatibility (Martin?), I have to say that while 'until' isn't formally described in the Axiom Book (like many other things we happen to use and like about AXIOM), it is was deliberately implemented in the compiler and the interpreter. On the semantics note: 'until' is not just an abbreviation for 'while not'. With 'until', the test is not after the body of the loop is executed. Which means the body is executed at least once. Whether they are redudant is a never-ending source of length debates over the last 60 years or so in the history of control structures. If we are going to remove things because they are perceived redundant, I propose to retrain only 'repeat' and remove all the other iterators. They just abbreviations for some test-and-exit instructions. -- Gaby ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ open-axiom-devel mailing list open-axiom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-axiom-devel
