4:13:39pjbcnomad: in the golden age of Internet, you could just do whois lispm.de # but this time has been over for a long time, since the spammers, etc.
4:13:58pjbAh, the good old golden age of the Internet…
12:03:34pjbfivo: what this tutorial means to convey, is that you should define and document your own API. It is valid to define make-instance '<your-class> as the API to instanciate objects of your class, and to specify that they're CLOS object.
12:03:43no-defun-allowedYes, that's also a good idea.
12:04:26pjbfivo: but if you could want to implement them as structures or as something else (eg. a reference in a database, a handle), then you may want not to publicise the fact that they're clos objects and it's a class.
12:05:02pjbfivo: in that case, you would define your API in terms of functions such as make-person, instead of a clos class with a constructor such as make-instance 'person.
12:05:54pjbfivo: and yes, you get to choose the precise list of accessors you want to export. Some accessors may be "private".
12:07:19pjbSince CL is a lisp-n, (cf. lisp-2 vs. lisp-1) a symbol can name several things. When you export it, thru it you give access to all the things it names.
12:11:17fivook so there is no mechanism to automatically export all accessors whenever I export the symbol of clos class? (maybe also for a good reason)
12:12:27no-defun-allowedYou can write a macro to do that.