llparse 0.1.9__tar.gz → 0.2.0__tar.gz

{llparse-0.1.9 → llparse-0.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: llparse
-Version: 0.1.9
+Version: 0.2.0
 Summary: A Parody of llparse written for writing C Parsers with Python
 Author-email: Vizonex <VizonexBusiness@gmail.com>
 Requires-Python: >=3.9
@@ -15,15 +15,16 @@ Dynamic: license-file
 
 A python parody of the typescript library llparse.
 
-I take no credit for the orginal work done by indutny and the other node-js contributors involved and I was originally very nervous about making 
-this python library that I made public... 
+I take no credit for the orginal work done by indutny and the other node-js contributors involved and my additional 
+features were meant to inspire activity with the original library again.
 
 Links to the original library 
 - https://llparse.org
 - https://github.com/nodejs/llparse
 
 Unlike the typescript library all 3 of llparse's libraries were combined in this version of the code for the sake of portability... 
-I ended up mentioning how I did this a while back and I also had a concept for a C parser as well but I just didn't like it and I ended up using this instead but I also learned typescript as a bonus and It was alot of fun for me. I don't plan to make this into a real pypi library yet but I also didn't want to take away from the magic of the original source code that I borrowed from...
+I ended up mentioning how I did this a while back and I also had a concept for a C parser as well but I just didn't like it and I ended up using this instead but I also learned typescript as a bonus and It was alot of fun for me. I don't plan to make this into a real pypi library yet but I also didn't want to take away from the magic of the original source code that I borrowed from.
+
 
 # Looking back on my dead work 2 years later
 I had this idea lay somewhat dormant for 2 years and now seeing that I wanted to write a new socks5 server parser writing it in python
@@ -134,3 +135,9 @@ open("http_parser.h", "w").write(c.header)
 
 ## Video Showcasing this library
 - https://youtu.be/YQOzJ2BghQw
+
+## Examples of this library being in use
+- [llh2](https://github.com/Vizonex/llh2) I would like to move to the typescript version once my ideas and
+  features I've added in get fully implemented but we shall wait and see...
+
+

{llparse-0.1.9 → llparse-0.2.0}/README.md

@@ -5,15 +5,16 @@
 
 A python parody of the typescript library llparse.
 
-I take no credit for the orginal work done by indutny and the other node-js contributors involved and I was originally very nervous about making 
-this python library that I made public... 
+I take no credit for the orginal work done by indutny and the other node-js contributors involved and my additional 
+features were meant to inspire activity with the original library again.
 
 Links to the original library 
 - https://llparse.org
 - https://github.com/nodejs/llparse
 
 Unlike the typescript library all 3 of llparse's libraries were combined in this version of the code for the sake of portability... 
-I ended up mentioning how I did this a while back and I also had a concept for a C parser as well but I just didn't like it and I ended up using this instead but I also learned typescript as a bonus and It was alot of fun for me. I don't plan to make this into a real pypi library yet but I also didn't want to take away from the magic of the original source code that I borrowed from...
+I ended up mentioning how I did this a while back and I also had a concept for a C parser as well but I just didn't like it and I ended up using this instead but I also learned typescript as a bonus and It was alot of fun for me. I don't plan to make this into a real pypi library yet but I also didn't want to take away from the magic of the original source code that I borrowed from.
+
 
 # Looking back on my dead work 2 years later
 I had this idea lay somewhat dormant for 2 years and now seeing that I wanted to write a new socks5 server parser writing it in python
@@ -124,3 +125,9 @@ open("http_parser.h", "w").write(c.header)
 
 ## Video Showcasing this library
 - https://youtu.be/YQOzJ2BghQw
+
+## Examples of this library being in use
+- [llh2](https://github.com/Vizonex/llh2) I would like to move to the typescript version once my ideas and
+  features I've added in get fully implemented but we shall wait and see...
+
+

{llparse-0.1.9 → llparse-0.2.0}/llparse/C_compiler.py

@@ -176,7 +176,7 @@ class CCompiler:
             posField = ctx.spanPosField(span.index)
 
             if len(span.callbacks) == 1:
-                cb = ctx.unwrapCode(span.callbacks[0], True)
+                cb = ctx.unwrapCode(span.callbacks[0])
                 callback = ctx.buildCode(cb)
 
             else:

{llparse-0.1.9 → llparse-0.2.0}/llparse/compilator.py

@@ -620,7 +620,7 @@ class SpanStart(Node):
 
         if len(field.callbacks) > 1:
             cbField = ctx.spanCbField(field.index)
-            callback = ctx.unwrapCode(self.ref.callback, True)
+            callback = ctx.unwrapCode(self.ref.callback)
             out.append(f"{cbField} = {ctx.buildCode(callback)};")
 
         otherwise = self.ref.otherwise
@@ -648,7 +648,7 @@ class SpanEnd(Node):
         out.append(f"{posField} = NULL;")
 
         # Invoke callback
-        callback = ctx.buildCode(ctx.unwrapCode(self.ref.callback, True))
+        callback = ctx.buildCode(ctx.unwrapCode(self.ref.callback))
 
         out.append(f"err = {callback}({ctx.stateArg()}, start, {ctx.posArg()});")
 
@@ -1121,8 +1121,7 @@ class Compilation:
     def reserveSpans(self, spans: list[_frontend.node.SpanField]):
         for span in spans:
             for callback in span.callbacks:
-                cb = self.unwrapCode(callback)
-                if cb:
+                if cb := self.unwrapCode(callback):
                     self.buildCode(cb)
 
     def debug(self, out: list[str], message: str):

{llparse-0.1.9 → llparse-0.2.0}/llparse.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: llparse
-Version: 0.1.9
+Version: 0.2.0
 Summary: A Parody of llparse written for writing C Parsers with Python
 Author-email: Vizonex <VizonexBusiness@gmail.com>
 Requires-Python: >=3.9
@@ -15,15 +15,16 @@ Dynamic: license-file
 
 A python parody of the typescript library llparse.
 
-I take no credit for the orginal work done by indutny and the other node-js contributors involved and I was originally very nervous about making 
-this python library that I made public... 
+I take no credit for the orginal work done by indutny and the other node-js contributors involved and my additional 
+features were meant to inspire activity with the original library again.
 
 Links to the original library 
 - https://llparse.org
 - https://github.com/nodejs/llparse
 
 Unlike the typescript library all 3 of llparse's libraries were combined in this version of the code for the sake of portability... 
-I ended up mentioning how I did this a while back and I also had a concept for a C parser as well but I just didn't like it and I ended up using this instead but I also learned typescript as a bonus and It was alot of fun for me. I don't plan to make this into a real pypi library yet but I also didn't want to take away from the magic of the original source code that I borrowed from...
+I ended up mentioning how I did this a while back and I also had a concept for a C parser as well but I just didn't like it and I ended up using this instead but I also learned typescript as a bonus and It was alot of fun for me. I don't plan to make this into a real pypi library yet but I also didn't want to take away from the magic of the original source code that I borrowed from.
+
 
 # Looking back on my dead work 2 years later
 I had this idea lay somewhat dormant for 2 years and now seeing that I wanted to write a new socks5 server parser writing it in python
@@ -134,3 +135,9 @@ open("http_parser.h", "w").write(c.header)
 
 ## Video Showcasing this library
 - https://youtu.be/YQOzJ2BghQw
+
+## Examples of this library being in use
+- [llh2](https://github.com/Vizonex/llh2) I would like to move to the typescript version once my ideas and
+  features I've added in get fully implemented but we shall wait and see...
+
+

{llparse-0.1.9 → llparse-0.2.0}/llparse.egg-info/SOURCES.txt

@@ -32,6 +32,7 @@ llparse/pyfront/namespace.py
 llparse/pyfront/nodes.py
 llparse/pyfront/peephole.py
 llparse/pyfront/transform.py
+tests/test_compilator.py
 tests/test_frontend.py
 tests/test_loop_checker.py
 tests/test_span_allocator.py

{llparse-0.1.9 → llparse-0.2.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "llparse"
-version = "0.1.9"
+version = "0.2.0"
 description = "A Parody of llparse written for writing C Parsers with Python"
 readme = "README.md"
 authors = [

llparse-0.2.0/tests/test_compilator.py

@@ -0,0 +1,54 @@
+# The good old http_parser was borrowed from llparse.org to demonstrate this for you :)
+from llparse import LLParse
+
+
+def test_http_parser_example():
+
+    p = LLParse("http_parser")
+    method = p.node("method")
+    beforeUrl = p.node("before_url")
+    urlSpan = p.span(p.code.span("on_url"))
+    url = p.node("url")
+    http = p.node("http")
+
+    # Add custom uint8_t property to the state
+    p.property("i8", "method")
+
+    # Store method inside a custom property
+    onMethod = p.invoke(p.code.store("method"), beforeUrl)
+
+    # Invoke custom C function
+    complete = p.invoke(
+        p.code.match("on_complete"),
+        {
+            #  Restart
+            0: method
+        },
+        p.error(4, "`on_complete` error"),
+    )
+
+    method.select(
+        {
+            "HEAD": 0,
+            "GET": 1,
+            "POST": 2,
+            "PUT": 3,
+            "DELETE": 4,
+            "OPTIONS": 5,
+            "CONNECT": 6,
+            "TRACE": 7,
+            "PATCH": 8,
+        },
+        onMethod,
+    ).otherwise(p.error(5, "Expected method"))
+
+    beforeUrl.match(" ", beforeUrl).otherwise(urlSpan.start(url))
+
+    url.peek(" ", urlSpan.end(http)).skipTo(url)
+
+    http.match(" HTTP/1.1\r\n\r\n", complete).otherwise(
+        p.error(6, "Expected HTTP/1.1 and two newlines")
+    )
+
+    # if this build fails in any way then we have failed...
+    c = p.build(method)