[Ecls-list] Unicode: uncomfortable situation

[Marko Kocić]

I don't see a reason why ECL would keep having feature-X disabled by
default if it already support it fully. I see the point in disabling
it only if it is highly an experimental feature. Features that are
enbled by default will certainly have much more testing in user code
then other.

As long as those features could be easily disabled in custom builds by
users that need smaller runtime, a bit faster execution, easier
embedding or whatever, I can't see a point in keeping them disabled by
default. I think the same about unicode and threads.

Just my 0.02€

On Sun, Jan 23, 2011 at 12:08 PM, Juan Jose Garcia-Ripoll
<juanjose.garciaripoll at googlemail.com> wrote:
> It seems that right now ECL can not be built without Unicode if one is to
> use _any_ of the really useful libraries.
>
> Almost all software around depends on flexi-streams and cl-unicode or some
> similar software, which simply does not work if char-code-limit is <= 65535.
>
> Should we just force Unicode by default? I do not want to keep getting
> random bug reports about cl+ssl and other software which is broken in that
> sense.
>
> Juanjo
>
> --
> Instituto de Física Fundamental, CSIC
> c/ Serrano, 113b, Madrid 28006 (Spain)
> http://juanjose.garciaripoll.googlepages.com
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Ecls-list mailing list
> Ecls-list at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ecls-list
>
>