16:17:37kagevfpdietz: by default a fasl file is generated in the same folder as the original *.lisp, or you can do something like (setq slime-compile-file-options '(:fasl-directory "/tmp/slime-fasls/")) ... from: https://slime-tips.tumblr.com/
16:49:12dbottonI created a class in one package and instance of that class in another, I've noticed if I need to access a slot value I need to specify the package for the slot name - (slot-value some-obj 'clog::slot-name)
16:59:41shkaanyway, it is easy to get used to it, simply by practice
16:59:43beachdbotton: Slots are implementation details. You should use functions instead. And the names of those functions should be prefixed with the package name as well, to indicate where the protocol function belongs.
17:02:47shkayeah, using slot-value is actually not the best idea
17:04:11beachThat's not the issue. The issue is that some attribute could be either stored or computed, and client code should not have to care which one, since it may change in future versions of the module.
17:04:17shkathere is obviously POD, but i would argue that POD type names should not be even exported
17:04:50shkabeach: yes, as I said, not very OO of you ;-)
17:05:08shkathat's the point: behavior, not data layout
17:06:02shkadbotton: hopefully this clears it up, do you have other questions?