The internal encoding is limited to 256. If we ever get close to that we can easily extend it, whence the sky is the limit.
On Mon, Oct 14, 2013 at 4:13 PM, Dan Bron <[email protected]> wrote: > Does this imply that J is limited to ~128 primitives? Estimating quickly, > we're pretty close to that limit already. > > -Dan > > Please excuse typos; composed on a handheld device. > > > On Oct 14, 2013, at 12:36 PM, Roger Hui <[email protected]> > wrote: > > > > They are special internally so that each verb/adverb/conjunction can be > > encoded by a single byte. It is a bug that the encoding is visible to > the > > user. > > > > > > > >> On Mon, Oct 14, 2013 at 9:34 AM, Devon McCormick <[email protected]> > wrote: > >> > >> Why is the top half of a. special? I would think that all the > documented > >> words J cares about are in the lower half. > >> > >> > >> On Mon, Oct 14, 2013 at 11:34 AM, Roger Hui <[email protected] > >>> wrote: > >> > >>> Convert 232 to hex and start looking for that. > >>> > >>> It'd be a really bad idea to depend on those encodings as that is > >> internal > >>> and may change without notice. > >>> > >>> > >>>> On Mon, Oct 14, 2013 at 8:26 AM, Don Guinn <[email protected]> > wrote: > >>>> > >>>> The top half of a. is special when executing a sentence. Codes are > >>> assigned > >>>> to those bytes. I looked for the source but haven't found it yet. > >>>> > >>>> On Oct 14, 2013 8:50 AM, "Devon McCormick" <[email protected]> > >> wrote: > >>>> > >>>>> I have no expectation of the output. I only found it because I was > >>>>> checking all character combinations in a "try...catch" phrase to > >>>> determine > >>>>> which ones don't give an error. > >>>>> > >>>>> I did try it in J6 and it behaves the same way. I don't know if I > >>> have a > >>>>> copy of J5 anywhere. > >>>>> > >>>>> It's not important - it's just something that passes my simple test > >> yet > >>>> is > >>>>> not really a known J word. > >>>>> > >>>>> > >>>>> > >>>>> On Sun, Oct 13, 2013 at 11:47 PM, bill lam <[email protected]> > >>> wrote: > >>>>> > >>>>>> The string is invalid as utf8, what would you expect the output > >>>>>> should be? Not sure how it will run under J504. > >>>>>> > >>>>>> Вс, 13 окт 2013, Devon McCormick писал(а): > >>>>>>> While experimenting with executing randomly-generated snippets of > >>> J, > >>>> I > >>>>>> ran > >>>>>>> across this: > >>>>>>> > >>>>>>> (232{a.),'3' > >>>>>>> Φ3 > >>>>>>> ".(232{a.),'3' > >>>>>>> > >>>>>>> $".(232{a.),'3' > >>>>>>> 0 > >>>>>>> {.".(232{a.),'3' > >>>>>>> 0 > >>>>>>> '1 2 3',(232{a.),'3 4 5' > >>>>>>> 1 2 3Φ3 4 5 > >>>>>>> ".'1 2 3',(232{a.),'3 4 5' > >>>>>>> > >>>>>>> This high-bit character seems to return i.0 for any argument. > >>>>>>> > >>>>>>> -- > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
