Re: Change of contract in UT_URL_ENCODING.unescaped_utf8

Indeed,
The current gobo's trunk is not Void safe.
At ISE we converted (almost) all Gobo's libraries, and made this version
available at http://github.com/jocelyn/void-safe-gobo-eiffel/tree/master
(almost because currently the ools, tests, and some XSLT related classes
are not converted).

Since Eric doesn't have that much time to integrate the result of the
conversion, I send him small patches from time to time, so that the
official gobo's lib is converted slowly.
The integration sometime requires implementation or interface change to
avoid having dirty code, and there are still points such as
DS_TRAVERSABLE.internal_cursor which should be detachable for
invariant's purpose, which slow down (or even block the progression).

If you see at the code hosted at github (See previous link), you might
noticed the xml cluster has a lot of changes (mostly  check var /= Void
end) to make it Void safe. This is mainly due to the fact some of those
classes use different attribute according to other (boolean status
report) attribute.
So we end up with many "detachable" attribute, and whenever the code use
them, it needs to check if this is attached or not.

Anyway, the conversion goes slowly, but surely. I doubt the official
gobo will integrate all the changes for 6.4, but we never knows ... Eric
might have more time, and maybe someone can review the changes from the
xml cluster, and eventually redesign some part to make it more
void-safety friendly.

So my short answer to your question
1) the official gobo's libraries get converted+integrated incrementally
2) however, the fully converted gobo's lib are available at
http://github.com/jocelyn/void-safe-gobo-eiffel/tree/master

Hope this helps,
-- Jocelyn


Eric Bezault wrote:
> Colin Adams wrote:
>   
>> One client was the test case. I've added a check statement so that it
>> should pass Void-safety.
>>
>> Geant test_debug_ge and geant test_debug_ise both pass, but I presume
>> these are NOT running in Void-safe mode. Is there a way to check that
>> what I have done is sufficient?
>>     
>
> Jocelyn might give a better answer here, but my feeling is that
> the classes are not fully void-safe yet. What is done is incremental
> modifications towards void-safety. So running in void-safe mode
> would still trigger a lot of errors I guess.
>
>   


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com