Re: [gobo-eiffel-develop] UC_STRING.is_empty

[majkel k. <maj...@ep...>]

Eric, 

looking for the latest draft, i found that there was a final draft
written for ELKS2001 STRING. what about the nice decision? it is not
stated on the official nice pages.

starting the project in 1999, i wanted to base my uc_string code upon
the new nice standard, but i had to wait years for it becoming
available. so i decided to wait until the new standard will be accepted
by nice. 

how long will it take nice to decide? will it be some weeks or months?
if it is accepted, i'll change the code to be ELKS2001 conformant (first
checking whether SE, ISE, and Visual Eiffel will follow the proposal).
if it will take more time, i'll add some additional feature names (eg.
is_empty), and will mark the old ones later as obsolete.

if you now about nice accepting ELKS2001-STRING, please send me the
reference.

Eric Bezault wrote:

> Majkel,
> 
> NICE has decided to have the feature `is_empty' instead of
> `empty' is class STRING. Sven Ehrke has suggested that it
> would be nice if UC_STRING also had a feature named `is_empty'.
> Therefore, would it be possible to add this routine to  UC_STRING,
> and possibly make the old routine `empty' obsolete (do you know
> about the 'obsolete' Eiffel keyword?)?

--
maj...@ep...