Hello Udo,
Thursday, July 27, 2006, 8:53:10 PM, you wrote:
Ah, never mind, I get the strong feeling I really don't want to know all
this. When even Windows 98 has been end-of-lifed we should rely on the
Unicode API, if anything.
i don't think we can do this in _compiler's system libraries_
Hello Krasimir,
Wednesday, July 26, 2006, 10:46:13 AM, you wrote:
The FilePath abstraction was discussed a number of times and it
seems that people prefer an ADT representation instead of plain
String. I tend to agree. Maybe such ADT based library can be
integrated with some new IO
Hello Udo,
Wednesday, July 26, 2006, 9:41:58 PM, you wrote:
- parameterize the FilePath ADT on the character type, you get (FilePath
Word16) on Windows (which uses UCS-2, not UCS-4 and not UTF-16) and
if i correctly understand, UCS-2 uses 2 bytes for ANY char, while
UTF-16 uses 2 or 4
Hello Duncan,
Wednesday, July 26, 2006, 7:34:50 PM, you wrote:
Exactly. I believe, a FilePath should be an algebraic datatype.
Most operations on that don't have to be specified, because they are
simple and have an obvious effect. Add a system specific parser and a
system specific
I've been writing a Stringable class for my SoC project. You can
check out the code at
http://darcs.haskell.org/SoC/fps-soc/Data/Stringable.hs.
Spencer Janssen
On 7/23/06, Bulat Ziganshin [EMAIL PROTECTED] wrote:
Hello Brian,
Sunday, July 23, 2006, 1:20:36 AM, you wrote:
instance IString
Hello Brian,
Sunday, July 23, 2006, 1:20:36 AM, you wrote:
instance IString ByteString.Char8 ...
instance IString String ...
i think that we should ask Donald Stewart who is patronized SoC
project involving development of such type class. If he will say that
such type class is not developed,
Bulat Ziganshin wrote:
Hello Brian,
Sunday, July 23, 2006, 1:20:36 AM, you wrote:
instance IString ByteString.Char8 ...
instance IString String ...
i think that we should ask Donald Stewart who is patronized SoC
project involving development of such type class. If he will say that
such type
