alpha
Login
or
Join now
klauser.link
/
prx
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Prexonite, a .NET hosted scripting language with a focus on meta-programming and embedded DSLs
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
Pulls
Pipelines
prx
/
Prexonite
/
Compiler
/
Grammar
/
at
27552fd2daabbff3e4fee2c0c0883ce7ee2cdf6a
10 files
Christian Klauser
Migrate to .NET 8 & nullability annotations
2y ago
d1a63bf1
Footer.atg
Initial import.
19 years ago
Grammar.Readme.txt
Initial import.
19 years ago
Header.atg
Migrate to .NET 8 & nullability annotations
2 years ago
Parser.Assembler.atg
Migrate to .NET 8 & nullability annotations
2 years ago
Parser.Expression.atg
Migrate to .NET 8 & nullability annotations
2 years ago
Parser.GlobalScope.atg
Migrate to .NET 8 & nullability annotations
2 years ago
Parser.Helper.atg
Migrate to .NET 8 & nullability annotations
2 years ago
Parser.Statement.atg
Migrate to .NET 8 & nullability annotations
2 years ago
Scanner.Coco.atg
Initial import.
19 years ago
Scanner.atg
PRX-7 Tolerate #!/interpreter/line Add a special hack to the lexer and parser that let them tolerate `#!<until EOL>` at the beginning of a Prexonite Script file. The rules are not very strict at the moment (doesn't need to be the first bytes in the stream; may even show up after comments), not because it makes sense to support it but because it would be more difficult to forbid it. I didn't want to go for a solution that hooks itself in before the lexer because that would mean introducing an entirely new mechanism/concept to the translation pipeline. With a lexer/parser based solution, I'm re-using existing infrastructure, which is going to be better in terms of maintenance long term.
5 years ago