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

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

Projects

None yet

2 participants

@PuercoPop

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
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
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.

@fukamachi fukamachi referenced this issue in eudoxia0/docparser Jul 22, 2015
Merged

Support uiop:define-package #10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment