tokay
ioccc-obfuscated-c-contest
tokay | ioccc-obfuscated-c-contest | |
---|---|---|
4 | 87 | |
231 | 130 | |
0.9% | - | |
8.7 | 0.0 | |
about 1 month ago | over 4 years ago | |
Rust | HTML | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tokay
-
The Awk Programming Language, Second Edition
[0]: https://github.com/tokay-lang/tokay
- GitHub - tokay-lang/tokay: Tokay is a programming language designed for ad-hoc parsing, inspired by awk.
-
Hacker News top posts: May 13, 2022
Tokay Programming Language\ (21 comments)
-
Tokay Programming Language
I am very interested in this project as a "better awk" is something I have often fantasized about.
I read all of the documentation that's available on https://tokay.dev/tokay-docs/, but unfortunately it never really... describes itself? Many sections, including the section on "parselets" are just unwritten. "Consumable" values are mentioned but never described (there is a "stub" section that doesn't really explain what the term means).
It begins with a pretty detailed description of value "severity" but doesn't really motivate why the concept exists. (I think that it's (basically) a way to very concisely discard certain matches? When there are "more important" matches around them?)
There are no examples of how I could use Tokay to "parse" something -- there are lots of examples dotted through the docs, but none of them demonstrate working with structured file formats, and they feel a little bit contrived.
I'm not complaining here: this project is not making any false claims about its status, the docs are clearly and explicitly unfinished, it is very clear that Tokay is still under active development.
But I want to learn more about it! I came away from that with a sense that, this has the potential to be really useful to me, but without any concrete evidence to support that. I guess the next step is to download the source and start reading through the tests.
All this to say: please highlight some examples showcasing situations where Tokay shines! (Parsing CSVs containing quoted strings was making the rounds recently, right? What does that look like in Tokay?)
Oh, actually, the GitHub readme has an example that is more involved than any in the documentation: https://github.com/tokay-lang/tokay
_ : [ \t]+ # redefine whitespace to just tab and space
ioccc-obfuscated-c-contest
-
Making Rust supply chain attacks harder with Cackle
A semi-automated system that compares old unsafe code to new unsafe code would likely be really helpful here - say, a LLM prompted to investigate whether the new unsafe blocks are a significant difference in scope and documented intent from the old unsafe blocks. Unless the winners of https://www.ioccc.org/ are among your attackers, it's a pretty solid line of defense.
-
500 Lines or Less – Writing a useful program in fewer than 500 line code – AOSA
For that you can go savor the archives of IOCCC : https://www.ioccc.org/
-
The Awk Programming Language, Second Edition
>> Perl can also be hilariously unreadable: https://www.foo.be/docs/tpj/issues/vol4_3/tpj0403-0017.html
Most programming languages can be obfuscated. That does not mean people write code in those programming languages like that:
C: https://www.ioccc.org/
Javascript: view-source:https://www.google.com/
The truth is that insulting Perl is considered stylish by some, so many people do despite knowing little to nothing about Perl and having never used it.
-
Where can I find the juiciest, most complex and modern c++ code?
If you want the most complex, then probably here https://www.ioccc.org/
-
Suggestions for making my fizz buzz program as convoluted as possible?
Since someone already linked Enterprise FizzBuzz, I'll link The Obfuscated C Contest as a possible source of inspiration.
-
Radiation-hardened Quine: A quine that works after any one character is deleted
Or this one [3] that calculates pi by estimating its own surface area.
Or this one [4]. It's a lovers quarrel, written simultaneously in C and English. It's incredible, seriously, read it.
[0]: https://www.ioccc.org/
-
Even the K&R book implements a "C gibberish to English" translator
I wonder what sort of "English" it spits out when fed obfuscated C code
-
I can't fathom how any of those could be used.
OP is going to rage quit when he sees https://www.ioccc.org/
-
JavaScript forbidden practices. Part 5: orthogonality
I mean, its no https://www.ioccc.org/ entry
-
JavaScript forbidden practices. Part 4: self-documenting code
The International Obfuscated C Code Contest for all you brain damage needs.
What are some alternatives?
sparklines - Text-based sparklines for the command line mimicking those of Edward Tufte.
Removeddit - View deleted stuff from reddit
butter - A tasty language for building efficient software. WIP
rustcc - A (toy) C compiler written in Rust.
mech - 🦾 Main repository for the Mech programming language. Start here!
Anime-Girls-Holding-Programming-Books - Anime Girls Holding Programming Books
react-snippets - A sample of useful snippets in React
W3Schools - W3Schools Full Offline Version
textimg - Command to convert from color text (ANSI or 256) to image.
git-blame-someone-else - Blame someone else for your bad code.
erg - A statically typed language compatible with Python
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.