pfalcon

11 ms·

61.
by pfalcon 6y ago
> Anyone interested in following the course together during the holidays? To keep each other motivated etc. Hey, don't forget my little "advent of code" too: https://github.com/pfalcon/python-ast-hacki
62.
by pfalcon 6y ago
> disparaging comments about the dragon book How's that possible? It's a "keep it under your pillow" book. Whether you read it or not is a different question. I don't know anyone in the 'hood who wouldn&#x27
63.
by pfalcon 6y ago
Good, good. Reminds me that stealing your https://rubybib.org/ idea for Python is on my todo list for long time ... Actually, my own ref to the Library of Alexandria, initially done for a word of mouth, is a literal situati
64.
by pfalcon 6y ago
> Still, accessing the slot does not require a dictionary lookup, as it would for an ordinary instance attribute, which was the main point I was trying to make. I'm sorry but mapping a string (slot name) to an index [in an overdynam
65.
by pfalcon 6y ago
> Compilers as a subject is not helped by the most widely recommended book being the Dragon Book Is it? Even I, an outsider [to the modern university courses], see that the baseline quite shifted to the TigerBook (aka Appel - Modern Comp
66.
by pfalcon 6y ago
Please don't... your hobby proglingo... will go unmaintained... :-D
67.
by pfalcon 6y ago
> Not if you're writing an IDE. Phew, how boring! I know compiler people who (apparently) spend their time at dayjobs writing IDEs, then get back home and write books on ol' good "batch mode" processing. Can't wa
68.
by pfalcon 6y ago
> very little of it is written down > and papers to absorb it. I smell a contradiction. But I'm glad that even well-known industry people see it like that. It's not a common flu you can pick up at university library. It&#x27
69.
by pfalcon 6y ago
> why books on interpreters and compilers tend to avoid the question of parsing like the plague They avoid it like old boring anecdote everyone read yet in their childhood in a dragonbook. > parsing is over-emphasized in other books,
70.
by pfalcon 6y ago
> Most languages are context sensitive. Most language tools are context free. How did we go so wrong? We never did. We always knew that any real-world useful grammar is multi-level and attribute (well, it's constraint-based, though
71.
by pfalcon 6y ago
> Good error recovery / line blaming is still an active field of development. True. But let's get terminology straight: that's not a compiler science, that's parsing science. And it's no more compiler science tha
72.
by pfalcon 6y ago
> There is no such variance and new fashions in compilers every year. Indeed. Packrat is exactly an example of passing fad in parsing. I find it telling that you, an "optimizations expert" are so worried about ways to parse. Sh
73.
by pfalcon 6y ago
> Most uni courses seem to involve writing a "toy" solution from scratch, which is seldom the case in professional programming. Without writing a "toy" from scratch, one would never understand professional programming
74.
by pfalcon 6y ago
They aren't looked up by index into an array, they are looked up by name , even if stored in an array. Roughly, an object with __slots__ is a mutable counterpart of namedtuple. Both need to map a name into a field/slot index. Of
75.
by pfalcon 6y ago
Special-casing (only) ints and floats in VM is too trivial and a bloat for quite minor benefit. To start with, faster VMs are not VMs, but JITs. And they are able to specialize for arbitrary types, not just 2 random ones. I thought there we
76.
by pfalcon 6y ago
Start your own open-source project, and make process of contributing to it not "intimidating".
77.
by pfalcon 6y ago
As a shameless plug, here's a proposal on how to optimize some things in Python object system: https://github.com/pycopy/PycoEPs/blob/master/StrictMode.md . Implemented in my lightweight Python dial
78.
by pfalcon 6y ago
I'd like to start with saying that I love such titles (both writing myself and reading others'). I also to check up such claims, so opened up that PDF. First of all, it's not "book", but a short article (10 pages).
79.
by pfalcon 6y ago
0.5.8 major changes include: * Better support of ELF files for easier interoperability with host environment (e.g. while PPCI doesn't support shared libs, those can be linked with host `ld`). * Many improvements to C frontend. * Many i
80.
PPCI (Pure Python Compiler Infrastructure) 0.5.8(github.com)
3 points by pfalcon 6y ago|1 comments
81.
by pfalcon 6y ago
SSA is entirely about phi nodes. Otherwise, the page at the link above shows an "if" statement without goto's. And if you follow more links there, you'll see a "while" without goto's too. If you're in
82.
by pfalcon 6y ago
Welcome to the club (of Python compiler writers): https://github.com/pfalcon/awesome-python-compilers If you wouldn't like to repeat what many people before did, but would like to do something (potentially) new, f
83.
by pfalcon 6y ago
Believe or not, but there's sad irony that it can be "pronounced" both ways ;-).
84.
by pfalcon 6y ago
Look at github - there're 3.4K forks of MicroPython. The only difference of this one is that it's by the guy who wrote ~30% of MicroPython (so if you use MicroPython, you likely rely on a bunch of stuff written by me), and who con
85.
by pfalcon 6y ago
No, I implement a generic object-oriented language with elements of functional paradigm, amenable for small-size VM and JIT implementation, a Python dialect. Extensibility is also important goal, but of course, extensibility and JITtability
86.
by pfalcon 6y ago
Yes, I'm of that generation which (being student age) drooled over Lisp (in all its possible dialects), just the same as the current generation drools over Haskell or whatever. So yes, please take that comparison as going from one Lisp
87.
by pfalcon 6y ago
I'm not sure. My interest is in "Python first" approach, after all, the whole idea of developing a small Python implementation (first MicroPython, then Pycopy) was to write code in Python, not C/C++. Where interfacing wi
88.
by pfalcon 6y ago
> I don't think you'd use Pycopy to write a desktop or cloud application Believe it or not, but that's one of the messages the Pycopy project tries to convey: Software can be simple. And understandable. And you really can
89.
by pfalcon 6y ago
They're both. All that stuff comes from MicroPython for full disclosure. There's a bytecode VM and a rather primitive JIT. Such primitive that actually on modern designed-for-meltdown processors, bytecode VM actually runs faster t
90.
by pfalcon 6y ago
> "Good for desktop, cloud, constrained systems, microcontrollers, and just everything." might be a tad overambitious... I remember old good days, when each software project wanted to rule the world ;-).

More ›