flex
Cwerg
flex | Cwerg | |
---|---|---|
9 | 59 | |
3,436 | 398 | |
- | - | |
8.4 | 9.6 | |
2 days ago | 8 days ago | |
C | Python | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
flex
-
How to provide input file for Flex++?
I am using Flex++, which is Flex for C++ and I am having trouble setting the input file. Flex++ uses the FlexLexer class provided in FlexLexer.h to create the lexer object(https://github.com/westes/flex/blob/master/src/FlexLexer.h). In my main function I have
-
Do Regular Expressions only evaluate one line at a time?
Further applications of DFA and NFA: lex or flex, yacc or bison, and POE :-)
-
Cool C projects
How about writing a programming language using Flex and Bison? There are lots of good tutorials and examples out there.
-
Parser and Lexer bike-shedding
Some lexer generators (notably Flex) take input from a file handle by default. While you can always read a file into a string before passing it to the generated lexer, this is not seen as "the best" since you have to read in all the data into memory, which can be a lot.
-
A Good Tool for Resuming Parsers?
Ages ago, I loved writing domain-specific toy languages, and almost always used flex to generate lexers and GNU bison to generate the parser. I've begun a new toy project and I don't think those two will cut it this time, so I'm looking for other tools that integrate well with C++.
-
Please no
I don't understand :c don't lexers like Flex work off of regex rules? Isn't this the correct first step to parse it?
-
A work in progress C compiler from scratch
I wrote a C compiler using flex [1] and bison [2]. The glue between them is a bit hacky.
At some point ANTLR [3] looked promising, but these days I'd probably write a lexer and recursive descent parser by hand, then generate LLVM IR.
[1] https://github.com/westes/flex
-
Dealing with lex and yacc is DIFFICULT so little information is available about them!
github.com/westes/flex/releases
-
Qual’è il commento più assurdo che avete mai trovato nel sorgente di un software?
Un commento in flex, uno storico software, tanto per mostrare che anche i migliori fanno le cose alla buona.
Cwerg
-
Cwerg: C-like language that can be implemented in 10kLOC
Perhaps these have already been dealt with and I'm missing critical information. If so, my apologies. Great work, in any case.
[1] https://github.com/robertmuth/Cwerg/tree/master/FrontEnd#dis...
-
Where can I find resources and guides on how to build compiler backends?
Cwerg has backend that can be used as JIT and is written with readability in mind. Additional documentation can be found here: https://github.com/robertmuth/Cwerg/tree/master/Docs
- Most important language features not touched in the book "Crafting Interpreters"?
- Lack of resources in creating Assemblers from scratch.
-
Minimum ISA Capabilities to Support Most (Non-Interactive) Programs?
I defined a basic ISA-like IR for Cwerg. It has unlimited registers and no constraints on immediates.
-
How do you design a compiler and a language?
entire compiler front end ast nodes
-
Syntax Design
I was also going down the path of bike shedding concrete syntax for my language Cwerg before pulling the plug on that effort and just using s-exprs. I managed to make the s-expr quite succinct by carefully choosing the order of arguments so I can omit optional ones. Also very helpful was to use square brackets for list, e.g. (call fun-name [arg1 arg2]). This simplifies parsing a little bit and is easier on the eye. Here are some Code Examples
-
November 2022 monthly "What are you working on?" thread
I am iterating over the languages features for Cwerg's Frontend which aims to be a low level language with about the complexity of C but with some of the comforts of modern languages. I am especially happy with the choice of adding sum types. Relative to C the current feature set looks like this: Removed: * arrays decay to pointers * bitfields * separate compilation (more of a backend issue) * pre-processor * varargs * implcit type conversions * (untagged) unions * ++/-- * comma operator * implicitly nullable pointers * goto
- typed asts and codegen
- Features Compendium
What are some alternatives?
LKI - LKI's dotfiles.
mir - A lightweight JIT compiler based on MIR (Medium Internal Representation) and C11 JIT compiler and interpreter based on MIR
cpp-peglib - A single file C++ header-only PEG (Parsing Expression Grammars) library
tinycc - Unofficial mirror of mob development branch
imp - Imp is a statically typed and compiled scripting language with the goal of increasing programmer confidence.
asmjit - Low-latency machine code generation
ocean - Programming language that compiles into a x86 ELF executable.
bluebird - A work-in-progess programming language modeled after Ada and C++
Apollo-11 - Original Apollo 11 Guidance Computer (AGC) source code for the command and lunar modules.
asmdb - Instructions database and utilities for X86/X64 and ARM (THUMB/A32/A64) architectures.
owl - A parser generator for visibly pushdown languages.
boring-lang - A very boring programming language