From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!ra.nrl.navy.mil!dca6-feed2.news.algx.net!allegiance!newsfeed1.cidera.com!Cidera!skynet.be!skynet.be!ossa.telenet-ops.be!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: [not so] basic package question References: <3CC0C3D8.C76B0F00@interaccess.com> <4lmbi5q1f.fsf@beta.franz.com> <3CC7D09E.42A2AC89@setf.de> <3CC860AB.547EA4A5@setf.de> <4ofg7cw70.fsf@beta.franz.com> <3CC9558C.945C1E89@setf.de> <3228855740453508@naggum.net> <3CCA999C.EE4F13CE@setf.de> Mail-Copies-To: never From: Erik Naggum Message-ID: <3228920503727600@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 70 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Apr 2002 18:21:44 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1019931704 193.71.199.50 (Sat, 27 Apr 2002 20:21:44 MET DST) NNTP-Posting-Date: Sat, 27 Apr 2002 20:21:44 MET DST Xref: archiver1.google.com comp.lang.lisp:32387 * james anderson | i am not concerned directly with symbols in the "COMMON-LISP" package. i | am concerned that, when a program generation utility creates symbols in | other packages, it do so in a way which accommodates a similar | expectation with respect to symbols in user packages, but does not fail | if the expectation is not met. I need to sort out a few things to make sure I understand what you are talking about. (1) The expectations you want met are not simply that symbols in the common-lisp package are all upper-case and that the reader and printer may produce other cases. If it were, I would conclude that you would have no problem at all since you control the reader and printer. But you give contradicting information to this position, i.e., you continue to have problems. (2) If the expectation is not met, the only way that could happen as I see your situation is precisely if the symbols in the common-lisp package were not all upper-case. You appear to claim that this is not the problem. (3) I sense a confusion in how you believe the reader and printer control variables affect the reading and printing of symbols. This sense is strongly reinforced by the fact that you neglect to tell us what your settings are. | and generated code which included things roughly like this Is this output from something? The reason I ask is that it appears more than unlikely that either of {xmlns}||, {}id, {}dir, {xml}lang, or {}lang would survive a printer that would both need to write |html| and also be happy with :use and :nicknames. | second, select a case for the symbol name: | an attribute name is transformed or preserved in manner consistent with | readtable case Why? The readtable-case is completely irrelevant to you. It concerns the mapping from input string to symbol name, but if this is SGML, you already know that the names are case-insensitive and you can canonicalize any way _you_ want, or if this is XML, you already know that the names are case-sensitive, so you should perform no transformations at all. | a function name is also transformed or preserved in a manner consistent | with readtable case | a macro name is transformed so as to be the opposite case of the | function name. This part is _really_ weird. The macro appears to be a completely useless massive complication of the whole node creation process. Would you call it on its own? Why a macro in the first place? Why make a new macro for each element when one can do for all? The whole point of the macro seems to be to convert an argument property list to an association list where all properties with a nil (= #IMPLIED?) value are removed while converting from a keyword to some weird internal symbol. This appears to me to be an excellent case for data-driven programming, not code-driven. | (that this fails where the document definition includes mixed case name | is another problem.) Well, it is a pretty strong indicator that you screwed up the design. | i did not want to use the reader. i suppose, since the names are | produced by parsing a document definition and should be fairly safe, | that concern may be unwarranted. If this is so, where does the reader come in at all? /// -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief. Post with compassion: http://home.chello.no/~xyzzy/kitten.jpg