freenode/#lisp - IRC Chatlog
Search
21:43:49
jeosol
I recently had a chat with Fare about it. He no longer works on it. I got some errors and posted on #sbcl but no leads yet.
9:01:54
moon-child
lukego: it's not about mixins and documentation strings--you can have those either way--it's just row vs column approach to the expression problem
9:11:27
lukego
It's an interesting problem that unfolds. The first pins are easy, like "This pin has to be connected to ground", "this pin should not be connected", "this pin should have a wide copper trace." but now it gets interesting with "this pin should be connected to that other pin with a 1kΩ resistor in between" and so now I need a way for a pin on one part to "imply" a whole other part and a pair of connections
9:13:46
flip214
lukego: in the past, I've often started with keywords; went to lists; and then structure or classes as the amount of data to store became too unwieldy in a list.
9:13:51
lukego
and in a traditional CAD package you might leave this informal for the designer to worry about, or make it a design rule that is checked, but it would be neat to just do it automatically "defmacro style"
9:16:29
lukego
I think the fact that I'm using CLIM in this application makes me also lean towards using classes. Since then the types I'm defining also have a meaning in that universe e.g. to create presentation methods and so on. I noticed this with Smalltalk - whole classes might feel like overkill but they are darned handy places to hang extension methods for things like graphical inspectors.