Re: [gobo-eiffel-develop] Change of contract in UT_URL_ENCODING.unescaped_utf8

[Colin A. <col...@go...>]

OK.

On that basis I was prepared to check in my changes.

But one of the tests has failed - for geant, so I guess this cannot be
something I have changed, as it will not be using the URI stuff.

Anyway, the failing test is GEANT_FUNCTIONAL_ECHO_TEST.test_built_in_var.
The failing assertion is test_builtin_var_2 (diff between files
'out.txt' and 'out2.txt' at line 1)

I cannot find a file named out2.txt or out.txt.

2009/5/6 Eric Bezault <er...@go...>:
> 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.
>
> --
> Eric Bezault
> mailto:er...@go...
> http://www.gobosoft.com
>