libera/#commonlisp - IRC Chatlog
Search
8:31:04
pve
Hi! Can the effect of "shadowing-import" be achieved using some combination of other functions, like "shadow" and "import"? Or is "shadowing-import" really its own thing?
9:57:05
beach
pve: I don't think you can obtain that functionality with a combination of other functions.
13:07:07
pve
I had this idea about a CLOSsy framework for defining packages, but I'm not sure if it's a stupid one. Instead of (defpackage :my-package ...) one would do something like (clossy-package:make 'pve:my-kind-of-package :name "UTILS" ... [other initargs]), possibly wrapped with a suitable macro.
13:08:37
pve
so by specializing methods on pve:my-kind-of-package one could control various aspects of the package creation (and possibly more, readtables for instances)
13:31:04
pve
Bike: Well I was hacking on my capitalized-export library, and thought that it's kind of a bummer to have to first make the package, then in-package and then set the readtable, when I really just want to say what "kind" of file I'm working on right now, i.e (clossy-package:make 'pve:one-package-per-file-with-capitalized-export-enabled :UTIL) and have all three happen at once.
13:54:54
Bike
if you just want to combine defpackage+in-package+defreadtable+in-readtable that could just be a macro rather than a new kind of package
13:58:09
pve
Bike: Yes, absolutely! But for some reason I thought that a clossy approach would be more flexible and lead to better things.
14:00:17
pve
Like if I come up with another "kind" of file, it would be nice if the same framework could handle that too.