Re: [wxhaskell-devel] darcs patch: Use wxString_Length function instead of ... (and 3 more)

[shelarcy <she...@gm...>]

Pushed. These patches are very big. I hope  that this change works well in your
environment.

And I have a plan to commit big patch once again.

2009/1/13 shelarcy <she...@gm...>:
> Thu Jan  8 23:26:43 =93=8C=8B=9E (=95W=8F=80=8E=9E) 2009  shelarcy <shelarc=
> y...@gm...>
>   * Use wxString_Length function instead of getting wxString twice.
>
>  Tue Jan 13 18:46:41 =93=8C=8B=9E (=95W=8F=80=8E=9E) 2009  shelarcy <shelarc=
> y...@gm...>
>   * Refactor to use wxString instead of calling WString (wxChar) directly.
>   =
>
>   This change will be easy to add encoding mode. wxWidget 2.9 and 3.0 will
>   support to build UTF-8 mode. If we use wxChar directly, we must change
>   many part to support this build mode.
>   =
>
>   http://www.wxwidgets.org/develop/roadmap.htm
>   =
>
>   And we think we get some advantages from this change. utf8-string package
>   only support UTF-8, so we want to use full unicode support we must write
>   UTF-8 <-> UTF-16 <-> UTF-32 conversion layer, or we must support new UTF-=
> 8
>   build mode.
>   =
>
>   (C++0x and C1x will support new string charactor set types, char16_t and
>   char32_t. Haskell and wxWidgets will support these types if compiler
>   (e.g. gcc, VC) support theirs. If we use abstract layer to use string,
>   we can extend wxHaskell support soonly when compiler and library change.)=
>  =
>
>
> Tue Jan 13 19:47:55 =93=8C=8B=9E (=95W=8F=80=8E=9E) 2009  shelarcy <shelarc=
> y...@gm...>
>   * Remove unused eljtreectrl.cpp.
>
> Tue Jan 13 22:57:54 =93=8C=8B=9E (=95W=8F=80=8E=9E) 2009  shelarcy <shelarc=
> y...@gm...>
>   * Add int / C++ bool conversion function in wxc.

-- 
shelarcy <shelarcy hotmail.co.jp>
http://page.freett.com/shelarcy/