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

Consider renaming project to avoid confusion with Expat XML parser #2

Open
felixbuenemann opened this issue Mar 9, 2018 · 2 comments

Comments

@felixbuenemann
Copy link

Hey,

there is already a popular C library libexpat, which is also spelled Expat in short or Expat XML parser in full, so it might make sense to rename this project to something else to avoid confusion.

See: https://libexpat.github.io

@vic
Copy link
Owner

vic commented Mar 11, 2018

Hey,

Actually, before the v1.0 rewrite I was thinking of renaming it, or perhaps just creating another project for the rewrite, and since I already have three client code bases that use expat, I wouldn't like to break those dependencies. But again v0 -> v1 does require people maintaning those code bases to explicitly update the new version in the mix file haha. So it's just that I didn't think much about another name, but I'm open to suggestions :)

@vic
Copy link
Owner

vic commented Mar 12, 2018

How about just pam (Patterns as Macros), short and sweet.

pame could be pam expand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants