Hi, I agree with Jim that '<' should be the one and only basic specifier. The central question is how to specify equality. When I tried to assess the degree...
Here is an initial proposal for COMPARABLE. I think we can discuss this in one step, and vote on it in a block doing the different issues in separate votes, ...
Hi everybody! Before I start to call for discussion, let me say some words about .NET. Personally I do not share the general excitement. I see a strong...
... Hello, Arno. Actually, after Roger Browne took a break, it appears no one wanted to step into his large shoes and stand up with an agenda. So while you're...
It seems people are awake now ;-) Before everybody runs off in a different direction, here is a proposal for a schedule, annotated with some of the problems I...
... I guess we miss Roger's stewardship. It would be nice if someone takes over Roger's role if Roger is too busy. ... Go on working on ANY, COMPARABLE, then...
Hello everybody! After the mast major effort (STRING), it seems we have trouble continuing the good work. One thing we should think about is what is most...
... DS_ARRAYED_LIST if you want ARRAY storage of an integer indexed list. ... I think one point for the current situation is that ARRAY is a basic building...
Hello, ... and remove ... insert in the ... Yes it can. See the feature add(element: like item; index: INTEGER) in class COLLECTION. As for item removal, just...
Hello, a moment ago I realized that ARRAY lacks features to insert and remove items! (SmallEiffel can add_first, add_last, and remove, but not insert in the ...
... I've now updated the "Draft ELKS 2002 ARRAY" page... http://www.eiffel-nice.org/standards/wip/array/array2002proposal.txt ...which should now be consistent...
I was looking at this last night and wondered why I had written code which assumed subarray (min, max: INTEGER): like Current rather than subarray (min, max:...
... I agree we should inform the client, but then "may be shared or new" is also a valid spec. Really what this info gives you is whether you are able to...
... Immutable strings generally solve the "aliasing" problem as people can't modify it, but not really the object identity (=) one. They are distinct: you can...
... Looking at the comment, that the result must be a new string; could we use a postcondition: generating_type_new_string: Result /= generating_type Or would...
I'm travelling from today until 12 December (mostly in Australia). I'm not planning to have email contact. The current vote (ARRAY 'resize39;) will automatically...
Hello, In ELKS 2001 STRING we have the following feature inherited from COMPARABLE: three_way_comparison (other: like Current): INTEGER -- If current object...
You should soon receive an automatically-generated message from the YahooGroups polling system, inviting you to vote on the following proposal for class ARRAY:...
... OK, there seems to be general agreement on this style guideline. At the end of this message I have shown how existing features of STRING and ARRAY would...
... You are right. This error is in the explanatory notes rather than the class specification. This is an adopted standard, so this group can't change the text...
I'm using the "fast-track" method suggested by Franck Arnaud to "close off" the two minor proposals that we worked on earlier this month. The proposals, and...
A fairly trivial observation, but worth a word. The postcondition of count is consistent_with_bounds: Result = upper - lower + 1 The postcondition of (for...
... Nope. Ads are hardly noticeable when used through email. ... I don't think it's worth it while it's usable in email. Also the annoying ads on the web side...
... For non controversial things should we have a simpler procedure without a vote? You (or whoever maintains a spec) could say that unless someone explicitely...
Hello, A hyper-text version of ELKS 2001 is available here: http://www.gobosoft.com/eiffel/nice/elks01/index.html ... My guess is that "`is_lower39;, `is_upper'"...
... The most likely ELKS postcondition for 'item_code39; in class STRING would surely be: ensure result = item(i).code which would not allow you redefine...
... It seems to me that Eric has pointed out an error that is straightforward to correct. I offer the following candidate versions for consideration. The only...