Pentimal predefinitions, sets the current pointer variable to the given value 1-16. Pop value from the stack and store it in the current pointer variableĪrithmetic, pop stack and add current pointer variable, store result in pointer variableĪrithmetic, pop stack and subtract current pointer variable, store result in pointer variableĪrithmetic, pop stack and multiply by current pointer variable, store result in pointer variableĪrithmetic, pop stack and divide by current pointer variable, store result in pointer variable Push current pointer variable into the stack Output, writes out the current pointer variable as a rune Input request, reads a value from the user and stores it in the current pointer variable Different forms denote different start directions and wrapping behaviour ![]() Unicode does not provide representation for these, so the numbers are formed by using combining diacritics on a base Isa rune stave, U+16C1. To set a cell value, the pentimal numbering system is used. In code, the runes themselves are interpreted as commands. Interpreters may choose to provide a convenience output option to convert the runes to raw data, but this is not a provision or requirement of the language. Any modern data encoding can be represented in this way. Arbitrary digital data output is provided if the runes are taken in pairs, to represent hex bytes. There is no option for distinguishing between character and numeric output, which is in keeping with runes which could be used to equally represent words and numbers, depending on context. This allows human readable output in Old Norse. Output therefore is any of the 16 Younger Futhark runes, potentially separated by Null bytes. An actual 0 for arithmetic purposes is achieved by using an unassigned cell, None/ Null, as an operand. ![]() 0x0 represents the first rune Fehu, with value 1. There are 16 runes in the Younger Futhark sequence, these are representable by 4-bit nybbles, 0x0-0xF. Values in RunR are arbitrarily capped at 255, but we do not need the extra, junk characters. ᚱᚢᚾᛅᛦ stays true to its theme by only supporting character output in runes, which should be sufficient for all data output and communication. The author feels that obscure and obfuscated languages which are awkward to write but provide convenient ASCII and numeric outputs are lazy and inelegant. txt file is free by clicking on the export iconĬite as source (bibliography): Elder Futhark ᚠᚢᚦᚨᚱᚲ on dCode.ᚱᚢᚾᛅᛦ makes use of Younger Futhark short-twig runes (all of them), topped up with some Elder Futhark runes to represent less used functions. The copy-paste of the page "Elder Futhark ᚠᚢᚦᚨᚱᚲ" or any of its results, is allowed (even for commercial purposes) as long as you cite dCode!Įxporting results as a. ![]() Except explicit open source licence (indicated Creative Commons / free), the "Elder Futhark ᚠᚢᚦᚨᚱᚲ" algorithm, the applet or snippet (converter, solver, encryption / decryption, encoding / decoding, ciphering / deciphering, breaker, translator), or the "Elder Futhark ᚠᚢᚦᚨᚱᚲ" functions (calculate, convert, solve, decrypt / encrypt, decipher / cipher, decode / encode, translate) written in any informatic language (Python, Java, PHP, C#, Javascript, Matlab, etc.) and all data download, script, or API access for "Elder Futhark ᚠᚢᚦᚨᚱᚲ" are not public, same for offline use on PC, mobile, tablet, iPhone or Android app! Ask a new question Source codeĭCode retains ownership of the "Elder Futhark ᚠᚢᚦᚨᚱᚲ" source code. Estimation indicates that this language has been spoken by Germanic peoples from the second century to the eighth century AD.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |