Re: [Bug-apl] 'SYNTAX ERROR+ Tokenizer: No token for Unicode U+00A0 ( )'

[Rowan Cannaday]

Thanks!

It was indeed a keyboard issue.

On OSX I use the right alt to toggle the APL keyboard.

ALT+space inserts a non-breaking space character.

When I write APL I would absent-mindedly hold down the alt button while typing spaces, thus breaking my code.

More info here. However theres 6 different fixes and they all work for different versions of OSX and different editors.

https://superuser.com/questions/78245/how-to-disable-the-option-space-key-combination-for-non-breaking-spaces

On Fri, Sep 27, 2019 at 3:22 PM Dr. Jürgen Sauermann <mail@jürgen-sauermann.de> wrote:

Hi Rowan,

my best guess is that your terminal setting is incorrect.
0xA0 is the unicode for non-braking space which has no APL significance
and might come from a regular space (0x20) with the upper bit set.

Best Regards,
Jürgen

On 9/27/19 9:11 PM, Rowan Cannaday wrote:

Greetings y'all,

I wanted to ask a far more interesting question, but unfortunately I'm having APL keyboard issues.

I frequently get the following error when using gnu-apl on OSX. I have never had this problem on linux, using the APL x11 kbd.

> SYNTAX ERROR+ Tokenizer: No token for Unicode U+00A0 ( )

I regularly get 'DEFN ERROR+', for normal function definitions.

I regularly get 'SYNTAX ERROR++' for normal variable assignments.

All these issues are fixed when I enter the same code from linux/x11.

I am using the dyalog keyboard file from here:
https://www.dyalog.com/apl-font-keyboard.htm

I suspect it has more to do with the keyboard file and how it chooses to do unicode input, than the gnu-apl interpreter.

Does anybody have a link to an OSX compatible APL keyboard they use? Or ran into the same issue that they fixed somehow?

- Rowan