[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Confused ⎕UCS
From: |
Kacper Gutowski |
Subject: |
Re: Confused ⎕UCS |
Date: |
Sun, 22 Nov 2020 23:11:56 +0100 |
On Sun, Nov 22, 2020 at 03:19:19PM +0100, Dr. Jürgen Sauermann wrote:
Floating point and complex numbers are not allowed as to avoid interference
with ⎕CT (i.e. how should rounding be performed?).
I share your sentiment regarding the upper bound of the ⎕UCS domain,
but throwing a domain error on ⎕UCS1E2 looks like a bug to me too.
1E2 is clearly an integer regardless of the implementation details,
and I would be surprised if APL2 didn't accept it. I would expect
rounding to be the same as in all the other places that require
near-integers, like array indices.
The negative ones are also a bit weird. I wasn't aware of their
existence, and they seem to work in surprising ways when passed
to various variants of ⎕CR.
-k
- Confused ⎕UCS, Adám Brudzewsky, 2020/11/22
- Re: Confused ⎕UCS, Dr . Jürgen Sauermann, 2020/11/22
- Re: Confused ⎕UCS,
Kacper Gutowski <=
- Re: Confused ⎕UCS, Dr . Jürgen Sauermann, 2020/11/23
- APL2 Compatibility, Adám Brudzewsky, 2020/11/23
- Re: APL2 Compatibility, Dr . Jürgen Sauermann, 2020/11/24
- Re: APL2 Compatibility, Hans-Peter Sorge, 2020/11/26
- Message not available
- Message not available
- Message not available
- Re: APL2 Compatibility, Hans-Peter Sorge, 2020/11/27
- Re: APL2 Compatibility, Jay Foad, 2020/11/27
- Re: APL2 Compatibility, Dr . Jürgen Sauermann, 2020/11/28
- Re: APL2 Compatibility, Peter Teeson, 2020/11/28
- Re: APL2 Compatibility, Jay Foad, 2020/11/29
- Re: APL2 Compatibility, Dr . Jürgen Sauermann, 2020/11/29