Hi Eric,

On Fri, 17 Aug 2007 05:05:54 +0900, Eric Y. Kow <[EMAIL PROTECTED]> wrote:
> Out of curiosity, what's the motivation behind this patch?

Please see this patch's complete name.

> * Use Data.Time.getCurrentTime instead of (System.)Time.getClockTime to
> avoid build failure by generated non-UTF8 String

This is my Windows environment problem that I wrote almost one year ago.


In Sat, 02 Sep 2006 16:56:24 +0900, shelarcy <[EMAIL PROTECTED]> wrote:
> $ make
> ghc -c wxcore/src/Graphics/UI/WXCore/WxcClassTypes.hs -o 
> out/wx/imports/Graphics
> /UI/WXCore/WxcClassTypes.o -iout/wx/imports -odir out/wx/imports -hidir 
> out/wx/i
> mports  -fvia-C -package-name wxcore -Iwxc/include
>
> wxcore/src/Graphics/UI/WXCore/WxcClassTypes.hs:1:0:
>      lexical error at character '\65279'
> make: *** [out/wx/imports/Graphics/UI/WXCore/WxcClassTypes.o] Error 1
>
> This is a known problem except Ascii, Latin-1 and EUC user.
> If show System.Time.ClockTime, we can show string that passed by OS.
> Windows show local encoding String, although using Unicode internally.
>
> By this effect, sometimes code generator cause problem. So I have
> to change from shift_jis to utf-8 a few generated files.
>
> $ cd wxcore/src/Graphics/UI/WXCore/
> $ mv WxcClassTypes.hs WxcClassTypes.hs.orig
> $ iconv -f shift_jis -t utf-8 WxcClassTypes.orig > WxcClassTypes.hs

Compiling WxcClasses* also cause this problem. So I don't test
and develop wxHaskell smoothly. I have a headache from that.


Best Regards,

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

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
wxhaskell-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wxhaskell-users

Reply via email to