... I think Jim is entirely correct. The specification of 'is_equal' is precise and complete - for class ARRAY - but cannot be modified in descendants to take...
... Here's a summary of what we've done and where we're at: ARRAY: The current standard is ELKS 2000 ARRAY. Since then, we have approved some tweaks to this...
... Alexander Kogtenkov replied with the results for Visual Eiffel. How about someone running Alexander's program under the other compilers so that we can see...
... The most likely ELKS postcondition for 'item_code' in class STRING would surely be: ensure result = item(i).code which would not allow you redefine...
... It doesn't say that characters should be 8 bits and not 32 bits or whatever, does it? If my UC_STRING satisfies the specification of STRING (i.e. does not...
... I think I should add that I'm convinced that the best design would be to have STRING and UC_STRING at the same level with an ancestor sharing their common...
... That's correct, and it allows Unicode support to be added in two ways. With vendor support, CHARACTER can support Unicode directly. This allows STRING to...
... Aren't these postconditions rigorous enough to be relied on in those applications, while allowing redefinitions: same_type ("") implies Result = item...
... Your design strikes me as ambitious and masterful, and your classes are likely to be useful to many people until such time as compiler-support for Unicode...
... 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...
... That postcondition does not adhere to the "principle of least surprise", and does not seem consistent with the header comment (in ISE Eiffel 4.5): ...
... I've also problems with descendents of STRING, haven't investigated it but it has something to do with is_equal or whatever. Raises its head when comparing...
... Last year we decided not to worry about anything inherited from COMPARABLE unless it directly impacted on STRING. When we review COMPARABLE, we can fix up...
... 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...
Franck Arnaud
franck@...
Jan 12, 2002 12:07 am
2601
... I've done this sometimes in the past (on an ad-hoc basis) for minor changes, and have sometimes been criticised because people didn't realise the change...
... [...] ... Sorry I didn't follow up on this sooner, the weather was so nice here at home I had to go down to the Caribbean and experience a tropical storm...
A fairly trivial observation, but worth a word. The postcondition of count is consistent_with_bounds: Result = upper - lower + 1 The postcondition of (for...
... I agree, I prefer the word "definition" when we have one line that is defining a query. ... It's always my first thought to do exactly that, however, there...
James McKim
jcm@...
Jan 25, 2002 3:23 am
2605
... I did exactly that in determining the order in which to test compliance of an implementation. -- Peter Horan School of Computing and...
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...
... 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...
... 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...
There was no further discussion on the proposal to change several tag names from 'string_not_void' to 's_not_void', so I'm going to close this off now. ...
... Thanks for reporting this error, which was present in the ELKS 95 version of STRING and survived into ELKS 2001. ... We looked briefly at the comparable...
... NICE-4 predates the November 2001 vote, so it's true that the 13 November 2001 revision is not in NICE-4. ... Are you saying that it was the NICE-4 version...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
