Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lisp: introduce version 0.0 of lisp meta parser #4130

Draft
wants to merge 11 commits into
base: master
Choose a base branch
from

Conversation

masatake
Copy link
Member

This one is not S expression-based but still line-oriented. However, the meta parser supports all Lisp, EmacsLisp, Clojure, and Scheme like before.

  • parser versioning: definer: field and unknown/Y kind are introduced to Clojure and Scheme as a side effect.

…sing lambda

This is preparation for rewriting the Scheme parser based on
x-lisp.h.

Scheme as a syntactic sugar for defining procedures:

       (define (f x) ... means (define f (lambda (x) ...
       (define ((g x) y) ... means (define g (lambda (x) (lambda (y) ...))

findLispTagsCommon() must skip '(' to extract f from (define (f
... and g from (define ((g .... to work as a part of the Scheme parser.

Signed-off-by: Masatake YAMATO <[email protected]>
Copy link

codecov bot commented Dec 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.89%. Comparing base (79b0e39) to head (fc50b5f).
Report is 59 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #4130   +/-   ##
=======================================
  Coverage   85.89%   85.89%           
=======================================
  Files         239      239           
  Lines       58697    58661   -36     
=======================================
- Hits        50418    50389   -29     
+ Misses       8279     8272    -7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@masatake masatake added this to the 6.2 milestone Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant