Timeline for Hexadecimal and the Alphabet
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 30, 2019 at 9:38 | comment | added | user58988 | Actual link make jelly interpreter to segfault... There would be in the text what jelly version and the link point to that version...or not use a link | |
| Dec 22, 2015 at 1:27 | vote | accept | Downgoat | ||
| Dec 20, 2015 at 12:58 | comment | added | Adám | In the defense of Dennis: since Jelly uses less than 256 chars, one could trivially define a fork of Jelly that just uses ANSI chars. The only difference would be readability and ease of remembering what each function does. | |
| Dec 19, 2015 at 19:52 | history | edited | Dennis | CC BY-SA 3.0 | added 151 characters in body |
| Dec 19, 2015 at 19:44 | comment | added | Dennis | @Timwi Fair enough. I've added both to the post. | |
| Dec 19, 2015 at 19:43 | history | edited | Dennis | CC BY-SA 3.0 | added 1075 characters in body |
| Dec 19, 2015 at 19:38 | comment | added | Timwi | @Dennis: APL has a fixed, published, known encoding. I didn’t say you can’t score one character per byte; I just think you should post the answer that is actually 18 bytes in order to claim 18 bytes, and if you want to change the encoding in your interpreter, then your answer should state which old version of the interpreter understands the encoding you used in the answer. | |
| Dec 19, 2015 at 19:32 | comment | added | Dennis | @Timwi Re scoring, how is that different from every single APL answer on this site? Nobody actually uses the APL code page... The source code in the custom encoding is 0000000: 62 b6 8c 3a b7 85 2b 8e 25 b7 a3 b7 95 8e 88 53 83 3f b..:..+.%......S.? (xxd dump). It is only changing since the language is currently under development. The char table will be fixed later. | |
| Dec 19, 2015 at 19:29 | comment | added | Timwi | @Dennis: Yes, found it now. I think you’re making it too easy for yourself. You just put a line in your parser so that it can theoretically read a binary format in which each character is one byte, but you didn’t actually write your program in it. You wrote it in a Unicode-enabled editor using Unicode characters. You did not post the binary file that is actually 18 bytes, and even if you did, it will become invalid with every new instruction you add to the language. | |
| Dec 19, 2015 at 19:25 | comment | added | Dennis | @Timwi It's in this file: code = ''.join([char_table[i] for i in code]) | |
| Dec 19, 2015 at 19:22 | comment | added | Dennis | @Timwi Documentation is work in progress. I haven't documented the encoding yet, since it is still changing with every commit. The same goes for pretty much all other features... | |
| Dec 19, 2015 at 19:20 | comment | added | Timwi | @Dennis: Please provide documentation of that encoding, and preferably, the language too. Perhaps write an esolangs wiki article on it? That will increase its visibility too :) | |
| Dec 19, 2015 at 19:19 | history | rollback | Timwi | Rollback to Revision 1 | |
| Dec 19, 2015 at 19:18 | history | edited | Timwi | CC BY-SA 3.0 | Smallest encoding is UTF-8, 35 bytes |
| Dec 19, 2015 at 18:57 | comment | added | Dennis | @Downgoat It isn't. Jelly uses its own, custom encoding. The source code can be provided either in UTF-8 or as a binary file. | |
| Dec 19, 2015 at 18:56 | comment | added | Downgoat | Which encoding does this use? It doesn't look like UTF-8, or ISO-8859 | |
| Dec 19, 2015 at 18:52 | comment | added | J Atkin | What....is.....that....? | |
| Dec 19, 2015 at 18:47 | history | answered | Dennis | CC BY-SA 3.0 |