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

The API of uiop isn't (parse|scrape)d adequately #24

Open
PuercoPop opened this Issue Sep 29, 2013 · 2 comments

Comments

Projects
None yet
2 participants
@PuercoPop
Copy link

PuercoPop commented Sep 29, 2013

The quickdocs API page on uiop only lists the functions from the package.lisp file. It appears to be related to the fact that uiop defines a macro to define packages and the other package definitions are using that macro, define-package, instead of defpackage.

@fare

This comment has been minimized.

Copy link

fare commented May 6, 2015

Yes, there are a lot of other projects that do a better job parsing the API of UIOP. If you don't adopt one of them, one technique you might want to use is detecting the set of packages before and after loading the package and computing the difference.

@fare

This comment has been minimized.

Copy link

fare commented May 6, 2015

Also, the project page for uiop is NOT http://common-lisp.net/project/uiop/ which doesn't even exist. Try cliki.net or the asdf page on common-lisp.net.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.