screwtape, to programming
@screwtape@mastodon.sdf.org avatar

hey so how am I meant to know what got :mix'ed into a package as by #'uiop:define-package programmatically?
I'm using :class :package-inferred-system anyway, so I'm referring to packages by identifying the file they are identified with in a given system: Am I meant to just open the file, and then #'ASSOC :mix in (cddr (read)) ?

louis, to random
@louis@emacs.ch avatar

I am now finally looking at ASDF and the "package-inferred-system" extension ( thank you @screwtape )

Starting with release 3.1.2, ASDF supports a one-package-per-file style of programming, in which each file is its own system, and dependencies are deduced from the defpackage form or its variant, uiop:define-package.

https://asdf.common-lisp.dev/asdf/The-package_002dinferred_002dsystem-extension.html#The-package_002dinferred_002dsystem-extension

I'm wondering what other Common Lispers think about it and if you already use it in production.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • cisconetworking
  • mdbf
  • tacticalgear
  • magazineikmin
  • thenastyranch
  • rosin
  • everett
  • Youngstown
  • khanakhh
  • slotface
  • ngwrru68w68
  • kavyap
  • DreamBathrooms
  • JUstTest
  • InstantRegret
  • osvaldo12
  • GTA5RPClips
  • ethstaker
  • tester
  • Durango
  • normalnudes
  • anitta
  • modclub
  • cubers
  • Leos
  • provamag3
  • lostlight
  • All magazines