2004 18:23
| To: Wolfgang Jeltsch
| Cc: The Haskell Mailing List
| Subject: Re: [Haskell] RE: Hugs/GHC incompatibility
|
| hi,
| i am speculating here, but i guess that if double initializations were
to
| result in _|_ one would have to check if a cell has already been
| initialized,
| and if so repla
hi,
i am speculating here, but i guess that if double initializations were to
result in _|_ one would have to check if a cell has already been
initialized,
and if so replace it with _|_.
currently ghc probably simply overwrites the array elements.
i personally prefer ghc's behavior.
-iavor
Wolfg
Am Dienstag, 3. Februar 2004 18:17 schrieb Simon Peyton-Jones:
> > I think, I've found the problem. GHC seems to not implement
> > Data.Array.array correctly. The implementation doesn't adhere to the
> > following sentence from the Data.Array.IArray.array documentation: If any
> > two associations
| I think, I've found the problem. GHC seems to not implement
Data.Array.array
| correctly. The implementation doesn't adhere to the following sentence
from
| the Data.Array.IArray.array documentation:
| If any two associations in the list have the same index, the value
at that
| index is
On Wed, 21 Jan 2004, Wolfgang Jeltsch wrote:
> In addition, I would like as little undefinedness as possible, i.e.,
> different implementations behaving as similar as possible. So I'd be
> happy if the handling of duplicate indices was defined by the library
> specification.
I agree (in this cas
hello,
i don't quite agree with this.
if something is "undefined" as in the prelude, i should be able to prove
that this is the case
-- bottom is just another value, admitedly not a very nice one :-)
on the other hand, if something is undefined in the specification
(i.e. implementer can do whate
On 2004.01.21 15:03, Iavor S. Diatchki wrote:
> hi,
> not that it matters, but i think commonly when specifications say
> that something is undefined, that means that the behaviour can be whatever,
> i.e. the implementors can do what they like. this is not to be confused
> with the entity "undefi
On 2004.01.21 15:03, Iavor S. Diatchki wrote:
> hi,
> not that it matters, but i think commonly when specifications say
> that something is undefined, that means that the behaviour can be whatever,
> i.e. the implementors can do what they like. this is not to be confused
> with the entity "undef
Am Mittwoch, 21. Januar 2004 23:03 schrieb Iavor S. Diatchki:
> hi,
>
> not that it matters, but i think commonly when specifications say that
> something is undefined, that means that the behaviour can be whatever, i.e.
> the implementors can do what they like. this is not to be confused with the
hi,
not that it matters, but i think commonly when specifications say
that something is undefined, that means that the behaviour can be whatever,
i.e. the implementors can do what they like. this is not to be confused
with the entity "undefined" defined in the Prelude.
-iavor
Wolfgang Jeltsch wro
Am Mittwoch, 21. Januar 2004 21:52 schrieb Wolfgang Jeltsch:
> Hello,
>
> I have some code which runs fine with GHC/GHCi but signals
> Program error: undefined array element
> when run with Hugs. Does anyone know why this difference occurs and where
> I have to search for the cause of the erro
Hello,
I have some code which runs fine with GHC/GHCi but signals
Program error: undefined array element
when run with Hugs. Does anyone know why this difference occurs and where I
have to search for the cause of the error in my code?
Wolfgang
__
12 matches
Mail list logo
