Along with fixes for customer reported problems, Service Level 13
contains the following enhancements:
All platforms:
New external function ROUNDC provides high-performance commercial
rounding. The same function is available for mainframe APL2 in PTFs
UK41421 (TSO) and UK41422 (CMS).
The limit on the length of function lines is raised to 32767.
The Execute Controlled system function returns full stack information on
error.
Processor 15 adds support for arbitrary arrays and variable monitor
expressions.
Performance of access to linefeed-delimited text files is improved in
Auxiliary Processor 210.
Windows:
Popup documentation for APL characters is provided on the APL Assist
toolbar.
The current line may be selected for execution from the Session Manager
and Object Editor, with results displayed in a separate window.
Custom toolbar buttons can execute APL expressions.
Unicode characters may be entered using the numeric keypad.
The Library Manager and WSCOMP support comparing objects containing
Unicode characters.
Other development environment additions include Copy To... on the Log
pull-down menu, Trace All Labels and Stop All Labels on the Breakpoints
menu, and Close Popups on the Windows menu.
Service Level 13 is available through the Support option at the APL2
home page to customers with a Software Maintenance contract, or at the
following link:
http://www-01.ibm.com/support/entdocview.wss?rs=0&uid=swg24020828&NotUpdateReferer=
Further information on the new facilities will be found in the updated
APL2 User's Guide and on-line help after installing the service. A
complete list of fixes included in this level will be found in the
updated README (Unix systems) or "Service Information" (Windows systems)
file.
>
> Unicode characters may be entered using the numeric keypad.
>
How is that performed?
David Liebtag
Can you go the other way around and get the codepoint of the
character?
I copied a line from Dyalog APL into Word
c ← '≢⍴⌽⊖⍉≥'
I then used <alt>+x after each character and got
0063002021900020002722622374233D2296234922650027
Changing it back to the original line did not work.
I had to put a space between each 4 numbers in order to get the
original characters back.
If I changed it back without putting a space between each group of 4
almost worked but I had to start from left to right.
So it is not trivial to go back and forth between APL and Unicode.
Putting space between each group of 4 numbers gives me
c ← ' ≢ ⍴ ⌽ ⊖ ⍉ ≥ '
Not putting spaces gives
← '≢⍴⌽⊖⍉≥'
It is close to correct but after creating the c then the c in front of
the group of 4 numbers changed into a single character
Changing that character back gives
C0020
the problem there is the design of a quick fix applied to the Microsoft
keyboard driver to allow generalised Unicode input
how many hex digits should alt-X absorb before converting to a Unicode
character? 4 is sometimes more than enough, and sometimes not enough, so
the driver reads backwards until _either_ it has enough digits to define
a Unicode value, _or_ it encounters a character which is not a hex digit
that "C0020" looks like it has a trailing space, but where it came from
I can only guess
all the best . . . /phil
In J this works well both ways
3 u: 7 u: 'c ← ''≢⍴⌽⊖⍉≥'' '
99 32 8592 32 39 8802 9076 9021 8854 9033 8805 39 32
(4&u:) 99 32 8592 32 39 8802 9076 9021 8854 9033 8805 39 32
c ← '≢⍴⌽⊖⍉≥'
David Liebtag
This would be ideal to to transfer code around
⎕UCS 'c ← ''≢⍴⌽⊖⍉≥'' '
99 32 8592 32 39 8802 9076 9021 8854 9033 8805 39 32
⎕UCS 99 32 8592 32 39 8802 9076 9021 8854 9033 8805 39 32
c ← '≢⍴⌽⊖⍉≥'
12 10 $3 u: 7 u: a
73 102 32 97 108 108 32 99 111 109
109 117 110 105 99 97 116 105 111 110
32 116 111 32 116 104 101 32 102 111
114 117 109 32 119 101 114 101 32 105
110 32 110 117 109 98 101 114 115 32
119 101 32 112 114 111 98 97 98 108
121 32 119 111 117 108 100 32 110 101
101 100 32 65 80 76 32 111 114 32
74 32 102 114 111 110 116 32 101 110
100 115 32 116 111 32 116 104 101 32
98 114 111 119 115 101 114 46 32 32
32 32 32 32 32 32 32 32 32 32
(4&u:) 12 10 $3 u: 7 u: a
If all com
munication
to the fo
rum were i
n numbers
we probabl
y would ne
ed APL or
J front en
ds to the
browser.