On Sun, Mar 20, 2005 at 04:34:12AM +, Ian Lynagh wrote:
> On Sun, Mar 20, 2005 at 01:33:44AM +, [EMAIL PROTECTED] wrote:
> > On Sat, Mar 19, 2005 at 07:14:25PM +, Ian Lynagh wrote:
> > > Is there anything LC_CTYPE can be set to that will act like C/POSIX but
> > > accept 8-bit bytes as
On Sun, Mar 20, 2005 at 12:59:52PM +, Keean Schupke wrote:
> How can I do the following (ie what are the new API calls):
>
>Open a file with a name that is invalid in the current locale (say a
> zip disc from a computer with a different locale setting).
A new API is needed for this.
>
One thing I don't like about this automatic conversion is that it is
hidden magic - and could catch people out. Let's say I don't want to use
it... How can I do the following
(ie what are the new API calls):
Open a file with a name that is invalid in the current locale (say a
zip disc from a
On Sun, Mar 20, 2005 at 01:33:44AM +, [EMAIL PROTECTED] wrote:
> On Sat, Mar 19, 2005 at 07:14:25PM +, Ian Lynagh wrote:
>
> > Most importantly, though: is there any way to remove this file without
> > doing something like an FFI import of unlink?
> >
> > Is there anything LC_CTYPE can be
On Sat, Mar 19, 2005 at 07:14:25PM +, Ian Lynagh wrote:
> In the below, it looks like there is a bug in getDirectoryContents.
Yes, now fixed in CVS.
> Also, the error from w.hs is going to stdout, not stderr.
It's a nuisance, but noone has got around to changing it.
> Most importantly, thou
On Wed, Mar 16, 2005 at 11:55:18AM +, Ross Paterson wrote:
> On Wed, Mar 16, 2005 at 03:54:19AM +, Ian Lynagh wrote:
> > Do you have a list of functions which behave differently in the new
> > release to how they did in the previous release?
> > (I'm not interested in changes that will affe
On Wed, Mar 16, 2005 at 03:54:19AM +, Ian Lynagh wrote:
> Do you have a list of functions which behave differently in the new
> release to how they did in the previous release?
> (I'm not interested in changes that will affect only whether something
> compiles, not how it behaves given it compi
On 16 March 2005 03:54, Ian Lynagh wrote:
> On Tue, Mar 15, 2005 at 10:44:28AM +, Ross Paterson wrote:
>> On Mon, Mar 14, 2005 at 07:38:09PM -0600, John Goerzen wrote:
>>> I've got some gzip (and Ian Lynagh's Inflate) code that breaks
>>> under the new hugs with:
>>>
>>> : IO.getContents: p
On Tue, Mar 15, 2005 at 10:44:28AM +, Ross Paterson wrote:
> On Mon, Mar 14, 2005 at 07:38:09PM -0600, John Goerzen wrote:
> > I've got some gzip (and Ian Lynagh's Inflate) code that breaks under
> > the new hugs with:
> >
> > : IO.getContents: protocol error (invalid character encoding)
> >
On Tue, Mar 15, 2005 at 08:12:48AM -0600, John Goerzen wrote:
> > [...] but Hugs is now much stricter, because character streams now
> > use the encoding determined by the current locale (for the C locale, that
> > means ASCII only).
>
> Hmm, this seems to be completely undocumented.
It's mention
On Tue, Mar 15, 2005 at 10:44:28AM +, Ross Paterson wrote:
> On Mon, Mar 14, 2005 at 07:38:09PM -0600, John Goerzen wrote:
> > I've got some gzip (and Ian Lynagh's Inflate) code that breaks under
> > the new hugs with:
> >
> > : IO.getContents: protocol error (invalid character encoding)
> >
On Mon, Mar 14, 2005 at 07:38:09PM -0600, John Goerzen wrote:
> I've got some gzip (and Ian Lynagh's Inflate) code that breaks under
> the new hugs with:
>
> : IO.getContents: protocol error (invalid character encoding)
>
> What is going on, and how can I fix it?
A Haskell 98 Handle is a charac
12 matches
Mail list logo
