On Sun, Jul 10, 2016 at 6:14 PM, Don Guinn <dongu...@gmail.com> wrote: > I am not suggesting any change in the way char is handled except when > combining with wide. So programs not using wide would not be affected. Wide > is different from char as it is only Unicode. It has no other use. So any > time wide and char are mixed the char bytes are must be Unicode points. So > I looked at what U+80 through U+FF are. Some control codes of which I don't > understand and Latin-1 Supplement. There are many useful symbols in > this range. But how would they be entered?
I think what you are proposing is that J should be changed so that x #@,y does not always match x+&# y. And, also, I think that you are proposing that x,y should throw a domain error when one argument is type 131072 and the other is type 2 and the type 2 argument is not valid UTF-8? In other words, I think you are proposing append works like this: append=: dyad define if. 131074 = x +&(3!:0) y do. x ,&(7&u:) y else. x, y end. ) in place of current behavior, which is more like this: append=: dyad define if. 131074 = x +&(3!:0) y do. x ,&u: y else. x, y end. ) But, also, I think that you are also proposing that we currently do not adopt other parts of the unicode standard, such as many of those listed at http://unicode.org/reports/? Do you feel that this accurately reflects your current point of view? Thanks, -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
