CY EXCELLENT!!!
It's good to see someone taking the time and energy to document the background and primary information about the how and why of category and domain instruction. My hope is that this will be the way Axiom is developed in the future. The code can always be improved but the design decisions are vital. I'm trying to document existing code and the questions ALWAYS arise: "WHY is this code here?", "WHAT were they trying to do?", "WHERE is this code used?", etc. The questions arise even in code *I* wrote years ago. Coding is the easy part once you understand the issues. It is the understanding that takes a long time. I believe that writing down what you come to understand is what will make Axiom into a living system (in the Christopher Alexander sense). Write for the next generation who will have to maintain it and change it. Tim _______________________________________________ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer
