All public logs

Combined display of all available logs of Esolang. You can narrow down the view by selecting a log type, the username (case-sensitive), or the affected page (also case-sensitive).

• 03:51, 6 June 2025 Tpaefawzen talk contribs created page DisFuck (Created page with "'''DisFuck''' is a combination of brainfuck and Dis languages designed by User:Tpaefawzen in 2025. == Overview == Data type is unsigned integer 0-59049; stored to registers and/or memory cell. Has registers A, C and D. A is accumulator. Has program memory tape. Stores commands. Can support arbitrary length of comamnds. Iterated by register C. Has data memory tape with data size of at least 59049 cells. It is implementation-defined whether it wraps around...")
• 00:00, 6 June 2025 Tpaefawzen talk contribs created page User:Tpaefawzen/Sandbox (Created page with "'''DisFuck''' is a brainfuck derivative with features from Dis designed by User:Tpaefawzen. == Overview == Has registers A, C and D. Has program tape. Iterated by register C. Has memory tape with data size of at least 59049 cells. Iterated by register D. 8-bit-unit I/O. Possible exit statuses: Ok, NoMatchingBrace. Source file is list of commands. Interpretation procedure is as follows: #j")
• 01:35, 1 May 2025 Tpaefawzen talk contribs created page Talk:95-98 (Created page with "== About addition arithmetic command == Where will the result be stored? --~~~")
• 21:58, 20 April 2025 Tpaefawzen talk contribs moved page COMP-X to CAP-X (Wanted to explain language not architecture itself)
• 11:18, 20 April 2025 Tpaefawzen talk contribs created page COMP-X (Created page with "'''CAP-X''' is an assembly language for the imaginary computer architecture '''COMP-X''' that had been adopted for Japan Information Technology Engineers Examination since the first examination in 1970 until the language got replaced by CASL in 1985. == See also == * Wikipedia:ja:CAP-X Category:Before 1993 Category:Low-level")
• 04:45, 6 April 2025 Tpaefawzen talk contribs created page BubbleSort言語 (Commands and semantics)
• 03:46, 6 April 2025 Tpaefawzen talk contribs created page ユニケージ開発手法 (Created page with "'''ユニケージ開発手法''' (Unicage development method) or simply '''ユニケージ''' ('''Unicage''') is a software development method by USP研究所 (Universal Shell Programming Laboratory). With the method it is said that non-programmers can development business systems from scratch with shellscript. * [https://www.usp-lab.com/ USP研究所] * [https://www.unicage.eu/ Unicage] English site Category:Unknown year Category:esoteric subset")
• 03:05, 6 April 2025 Tpaefawzen talk contribs created page POSIX原理主義 (Created page with "'''POSIX原理主義''' (POSIX fundamentalism), also known as '''POSIXism''', or in more wide context '''POSIX中心主義''' (POSIX Centralism) is a software development method. Its intension is to make a sustainable and portable software using just POSIX-compatible shellscript with utilities standardized in POSIX. (Later, he had went to POSIX-C development to achieve that) It is essentially a kind of w:Shellscript subset. Because of coding style, it can be consid...")
• 11:06, 5 April 2025 Tpaefawzen talk contribs created page プログラマーのための古典音楽理論 (Created page with "'''プログラマーのための古典音楽理論''', also known as '''ClassicMusicTheoryForProgrammer''' [sic] is an esoteric programming language developed by GitHub user [https://github.com/lv100tomato lv100tomato] since 2019. The language https://github.com/hakatashi/esolang-battle/wiki/%E7%AC%AC6%E5%9B%9E%E6%9D%B1%E5%A4%A7%E4%BA%AC%E5%A4%A7%E3%82%B3%E3%83%BC%E3%83%89%E3%82%B4%E3%83%AB%E3%83%95%E5%A4%A7%E4%BC%9A-Writeup#classicmusictheoryforprogrammer-u6606u5e03...")
• 12:51, 28 March 2025 Tpaefawzen talk contribs created page User:Tpaefawzen (Profile)
• 12:45, 28 March 2025 Tpaefawzen talk contribs created page 257-wrap brainfuck (Created page with "'''257-wrap brainfuck''' is a brainfuck derivative published by Code Golf StackExchange user [https://codegolf.stackexchange.com/users/76323/l4m2 l4m2] in March 2022. == Overview == L4m2 criticized that usual brainfuck language (who uses 256-value as data type) has no way for the input command <code>,</code> and other commands to distinguish actual EOF from usual byte values such as x00 or xFF or others; l4m2 introduced using 256 as EOF value and merging I/O into on...")
• 12:20, 28 March 2025 User account Tpaefawzen talk contribs was created