5:18:47Josh_2Is it possible for me to modify the default behaviour of the automatically generated accessor functions that are created when I define a new class?
5:19:51beachSure, they are just methods on generic functions. You can add auxiliary methods, or you can redefine the primary method.
5:20:41beach... unless you mean that you want DEFCLASS to generate accessors that behave differently. That might be more complicated.
5:23:40Josh_2hmm, well my problem is that I have lots of different classes where the type is either a keyword or a byte array, however when it comes to actually using instances of those classes I have to manually convert from a byte array to a string, and I was wondering if I could just get the accessor functions to call the converting code for me
5:27:29beachThe easiest way would be to define a wrapper macro for DEFCLASS. The right (but more complicated) way would probably be to use the MOP in some creative way.
5:27:51pjbclim does just that. It defines its own defclass, so it can generate the accessors (and other things) as it wishes.