Understood. Thanks. I really wish they would allow people to upload their own games. Kinda like that old website (Newgrounds? idk).

This statement is completely wrong. Like, to a baffling degree. It kinda makes me wonder if you’re trolling.

No I just struggle at getting my meaning across + these stuff are new to me. What I meant was ‘Go does memory management LIKE a VM does’. Like ‘baking in the GC’. Does that make sense? Or am I still wrong?

I know about all this — I actually began implementing my own JVM language a few days ago. I know Android uses Dalvik btw. But I guess a lot of people can use this info; infodump is always good. I do that.

btw I actually have messed around with libgcc-jit and I think at least on x86, it makes zero difference. I once did a test:

– Find /e/ with MAWK -> 0.9s – Find /e/ with JAWK -> 50s.

No shit! It’s seriously slow.

Now compare this with go-awk: 19s.

Go has reference counting and heap etc, basically a ‘compiled VM’. I think if you want fast code, ditch runtime.

I think that happens when app developers learn2optimize. Stop using interpreted bytecode languages on small processors!

My man we have UNIX because PDP-11 was expensive!

True, but see, all these build up on the theoretical regex. The theoretical regex indeed has only 3 operators: dot for concatenation, pipe for alteration and the 'kleene star' [re: Sipser's]. These 3 operators can express a finite state automata. You don't really need all that other operators. Read this: https://swtch.com/~rsc/regexp/regexp1.html Algorithms like Thompson construction can translate a regex to a non-deterministic automata quite quickly, and then from there you can make a DFA or just simulate the NFA.

I would not call PCRE 'regular expression' really. If you read the article I gave you it explains why they are mostly a practical utility than a theoretical groundwork. The regex in use today is far from the regex one learns about in books.

I think regex is abused. People use it to parse context-free grammars. Extremely intricate and feature-rich patterns cause people to make mistakes, and end up with security holes!

That being said, I really enjoy NeoVim's regex. I also like Perl's. But I would not rely on them for parsing, or even lexing.

What should we talk about then, glob patterns (which are NOT regular expressions, for the love of all that is holy and unholy, stop calling glob patterns RE!)

Keep in mind that in OG regex, period is used to concat.

Removed by mod

I hope so.

Depends on what repositories/archives your Pacman pulls from. But you can just build Cool-Retro-Term yourself: https://github.com/Swordfish90/cool-retro-term

This also has an AppImage you could use.

People are designing languages with JetBrains MPS and I am making an AWK interpreter in C with Yacc, Lex and my own implementation of ASDL. Why do I do this to myself? It seems like the technology I like is way behind. Like C is a language created for freaking mini-computers like VAX and PDP-11 and I still use it? I knew about MPS, I just felt a strong dislike towards it. Now that I am no longer a pill addict, I have to reconsider the technology I choose to implement my stuff. C lacks portability, and QoL features.

(Psyche! All you n000bz can be stuck with your Fischer-Price toys — I'll do it MY way, the 70s WAY!!!1)

I really recommend creating a compiler or an interpreter from scratch, don't even use an IR like LLVM or MIR. Just hack and slash your way though a C compiler, it's the simplest language most people know. Don't care about 'optimization' at first, fuck optimization. Just grab Yacc/Lex or a PEG parser generator that works with the language you like most and have ot generate assembly code for simple expressions. Like, make a bc(1) native compiler! Interprets are fun too. You can use VMGEN to generate a superfast VM in C, and then bind it to another language using SWIG.
Also never imagine usability. Noobdy is going to use your C compiler for any serious work. It's just for education. Post it online to receive feedback.

You cna start by writing DSLs. For example, I am implementing the ASDL language from this old paper.

Also if you are going to do it as an example in your resume, just stop. Nobody cares, because it's a trivial task to write a compiler, even if you write backend, forntned, and the LP yourself! Do something money-loving people loike, like making some bullshit mobile app that tracks your gym sweat volume.