- cxml-devel - mailman3.common-lisp.net

[cxml-devel] Building cxml with recent versions of asdf
by Andy Chambers 29 May '10

29 May '10

Hi All, Building cxml seems to fail with recent versions of asdf. I get the error message in the linked paste. http://paste.lisp.org/display/110920 The attached patch was the minimum change I could make to get the system to load. Cheers, Andy -- Andy Chambers

1 0

[cxml-devel] installing cxml on sbcl 1.0.34.0.debian
by Lukas Gießmann 22 May '10

22 May '10

hi list, i have a problem with installing the latest cxml on sbcl 1.0.34.0.debian. after (asdf:operate 'asdf:load-op :cxml) i get the following message: --- Error while trying to load definition for system cxml from pathname /root/.sbcl/systems/cxml.asd: The value (MERGE-PATHNAMES "xml/" (MAKE-PATHNAME :NAME NIL :TYPE NIL :DEFAULTS *LOAD-TRUENAME*)) is not of type (OR (VECTOR CHARACTER) (VECTOR NIL) BASE-STRING PATHNAME FILE-STREAM). [Condition of type ASDF:LOAD-SYSTEM-DEFINITION-ERROR] --- has anyone an idea? best regards lukas _________________________________________________________________ http://redirect.gimas.net/?n=M1005xHM2 Entdecken Sie das mobile Einfach: Nutzen Sie Hotmail unterwegs!

2 1

[cxml-devel] DTD parsing
by Mariano Montone 04 May '10

04 May '10

Hi, I write because I have a problem with DTD validation. I can not parse the DTD The DTD I want to use is this: http://www.w3.org/TR/html4/strict.dtd But this is what I get when evaluating: (cxml:parse-dtd-file "/home/marian/Escritorio/strict.dtd") Document not well-formed: Expected :> saw :NMTOKEN ["--"] Context: Line 82, column 7 in file://+/home/marian/Escritorio/strict.dtd [Condition of type CXML:WELL-FORMEDNESS-VIOLATION] Does anyone know what may be wrong? I'm using the git version of cxml on sbcl. Thanks! Mariano

2 5

[cxml-devel] Patch - restart case for unbound prefix
by Red Daly 05 Feb '10

05 Feb '10

Hi, It is helpful to be able to catch the case when a prefix is used in an XML document without a proper declaration in the document. This patch provides a more specific condition class and a restart for using a particular value for the namespace uri when a prefix is unbound. Best, Red

1 0

[cxml-devel] the missing-dependency instantiation is invalid
by james anderson 04 Feb '10

04 Feb '10

good morning; with the current cxml source and asdf @1.502, the :version keyword causes an error[1]. to wit: ? (asdf:find-system "cxml" nil) ;Loading #P"/Development/Source/production/Library/asdf-registry/ cxml.asd"... > Error: :VERSION is an invalid initarg to INITIALIZE-INSTANCE for #<STANDARD-CLASS MISSING-DEPENDENCY>. > Valid initargs: (:REQUIRES :PARENT :REQUIRED-BY). > While executing: CCL::CHECK-INITARGS, in process Listener(6). > Type :POP to abort, :R for a list of available restarts. > Type :? for other options. 1 > either the keyword or the type must change. ------- [1]: http://repo.or.cz/w/cxml.git/blob/ 401d6e4e5d82ef880a02aed1f9226aa6dbc565c8:/cxml.asd#l15

1 0

[cxml-devel] Problems parsing HTML with embeded JS which itself embeds HTML
by Plamen . 23 Dec '09

23 Dec '09

Hello all, for a project I need the possibility to extract some info from a web page to link it with a database and have tried several html parsers for CL. I would like to use Closure HTML for the task because of the add ons for XPATH, but I have a problem parsing the HTML source I have with it. An example page describing the problem is for example HTML source of http://yellow.local.ch/de/q?ext=1&name=&company=Berufsschule,+Fachschule&st… from which I need to extract some of the address/street/phone data. It seems, that all HTML/XML parsers for CL can't parse it correctly and most of the missing parts in the parsed representation are the ones which deal with the HTML-source which defines a Javascript element which itself includes HTML as a string parameter in the embedded JS. Which is of course exactly the text which I need from the site :) Of course I could extract the data using some regexps but it's really clumpsy and if possible, it would be nice to can stay in the HTML/JS-parse/STP/XPATH data representation. I've looked in the source of Closure HTML to try to help, but it seems that the project has pretty old and deep roots in SGML, where I don't want to introduce errors - I don't know SGML and may be - even if I find the places needed to be corrected for HTML, that could brake something for the SGML part of Closure-HTML. Also, I think I would need not so short time to get the inner workings of the parsers in Closure-HTML, so I would greatly appreciate any help to get it working with the described site. With best regards Plamen

3 2

[cxml-devel] Parsing yields TEXT elements with #\Newline #\Tab
by Marco Antoniotti 07 Dec '09

07 Dec '09

Hi I have been (successfully) parsed some SBML files with CXML on LWM. However I noticed the following effect. I get all my actual RUNE-DOM::ELEMENTs interleaved with "bogus" TEXT elements containing just #\Newline and #\Tab (or more #\Tab). This is obviously an artifact of parsing. (See attached figure from a 15 minutes CXML browser I whipped up) What I do not know it's (1) whether this makes sense or not, or (2) whether it is dependent on my platform (LWM). Does this make any sense to you? Note that I was observing the sam effect with CL-XML. Cheers -- Marco Antoniotti

4 13

[cxml-devel] Error 'The value NIL is not of type VECTOR.' in '(defun normalize-text-nodes! ..)' when using atdoc
by Thijs Oppermann 21 Nov '09

21 Nov '09

As I mentioned in #lisp on irc I got the mentioned error in cxml-stp/xpath.lisp in normalize-text-nodes! (starts at line 191) when using atdoc with a completely fresh checkout of everything through clbuild. Apparently children is NIL when parsing base-uri.xml. I got it working again (at least, no error and atdoc seems to produce the correct docs), by changing the following in normalize-text-nodes!: (when (loop for child across children for a = nil then b for b = (typep ... into: (when (and children (loop for child across children for a = nil then b for b = (typep ... ) Don't know if that really fixes the problem, but it got me up and running again... Gr, Thijs

1 0

[cxml-devel] Problem loading CXML into 8-bit Allegro
by Scott L. Burson 08 Sep '09

08 Sep '09

Hi, I am trying to load Daniel Herring's LibCL metalibrary (which incorporates many other libraries including CXML; see http://libcl.com/) into Franz Allegro CL. Allegro, as you may know, has different executables for 8-bit and 16-bit characters. When loading into the 8-bit version, I ran into a minor problem that xml/unparse.lisp tries to set the documentation of MAKE-CHARACTER-STREAM-SINK, but that function is not defined in the RUNE-IS-INTEGER case. -- Scott

1 0

Re: [cxml-devel] cxml:doctype function
by Steven Nunez 21 Jun '09

21 Jun '09

Thanks, but that's still a newline within an element. It's a fine point, and not terribly important, but ideally we want is something that produces:  Cheers, - Steve --- On Sat, 6/20/09, David Lichteblau <david(a)lichteblau.com> wrote: From: David Lichteblau <david(a)lichteblau.com> Subject: Re: [cxml-devel] cxml:doctype function To: "Nunez Steve" <steve_nunez(a)yahoo.com> Cc: cxml-devel(a)common-lisp.net Date: Saturday, June 20, 2009, 3:20 PM Quoting Nunez Steve (steve_nunez(a)yahoo.com): > Thanks. What I am hoping for is a way to write multi-line comments. > cxml:text doesn't seem to work outside elements. Same approach. CL-USER> (cxml:with-xml-output (cxml:make-character-stream-sink *standard-output*) (cxml:comment (format nil "~%foo~%bar~%")) (cxml:with-element "test")) <?xml version="1.0" encoding="UTF-8"?> <test/>

2 1

[cxml-devel] cxml:doctype function
by Nunez Steve 20 Jun '09

20 Jun '09

Greetings All, Does anyone have an example of using the cxml:doctype function? The code indicates that the last argument is of type puri:uri, which I think I have in the following: (cxml:doctype "suite" "suite" (puri:uri "http://testng.org/testng-1.0.dtd")) however any use of this generates an error in CCL: value #http://testng.org/testng-1.0.dtd> is not of the expected type SEQUENCE. I'm using slime, but not sure if this is related. The same error occurs at the command line. Unfortunately, the documentation for puri seems to have moved, so beyond looking at the code (that I'm unfamiliar with), the best I can do is guess. I know this function is relatively new, so am wondering if it's been widely tested. Are there any alternatives to writing a XML doctype? I need to write quite a few, sometimes large, XML test suites for testng. Cheers, - SteveN

2 5

[cxml-devel] [ELS 2009] Call for participation
by Marco Antoniotti 20 May '09

20 May '09

Apologies for multiple postings.... ************************************************************************ 2nd European Lisp Symposium (ELS 2009) Milan, Italy, May 27-29, 2009 Universita` degli Studi di Milano-Bicocca www.european-lisp-symposium.org ************************************************************************ CALL FOR PARTICIPATION ********************** REGISTRATION IS OPEN AT www.european-lisp-symposium.org. Check out the updated program. Scope and Program Highlights: ***************************** The purpose of the European Lisp Symposium is to provide a forum for the discussion of all aspects of the design, implementation and application of any of the Lisp dialects. We encourage everyone interested in Lisp to participate. The European Lisp Symposium 2009 program includes presentations of high quality papers about novel research results, insights and lessons learned from practical applications, and educational perspectives, all involving Lisp dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, and so on. The European Lisp Symposium will feature the following highlights: - Scott McKay of ITA Software will talk about how Lisp use has evolved in his circannual industry work. - Mark Tarver of Lambda Associates will talk about Qi as a viral mutation of the Lisp DNA. - Mauro Pezze` of University of Milan-Bicocca will host a panel on Programmers' Productivity from a Software Engineering point of view. - Joao Pavao Martins and Ernesto Morgado of SISCOG will talk about the role of LISP in the success of SISCOG - Christophe Rhodes will give an unportable tutorial. - Michele Simionato will give a tutorial on Scheme module system and Scheme libraries portability issues across implementations. Social Events: ************** Friday 29th evening, Conference Banquet Saturday 30th morning, Guided tour to the "Futurismo" Exhibit in the center of Milan; 2009 marks the 100th anniversary of the Futurism Manifesto; stretching it, the harbinger of Lisp 50 years later. Program Chair: ************** * Antonio Leitao, Technical University of Lisbon, Portugal Local Chair: ************ * Marco Antoniotti, DISCo, Universita`† Milano Bicocca, Italy Program committee: ****************** * Giuseppe Attardi, Universita` di Pisa , Italy * Pascal Costanza, Vrije Universiteit Brussel, Belgium * Irene Durand, Universite` Bordeaux 1, France * Marc Feeley, Universite` de Montreal, Canada * Ron Garret, Amalgamated Widgets Unlimited, USA * Gregor Kiczales, University of British Columbia, Canada * Scott McKay, ITA Software, Inc., USA * Peter Norvig, Google Inc., USA * Julian Padget, University of Bath, UK * Kent Pitman, HyperMeta, USA * Christian Queinnec, Universite` Pierre et Marie Curie, France * Christophe Rhodes, Goldsmiths College, University of London, UK * Robert Strandh, Universite` Bordeaux 1, France * Mark Tarver, Lambda Associates, UK * Didier Verna, EPITA Research and Development Laboratory, France * JonL White, TheGingerIceCreamFactory of Palo Alto, USA * Taiichi Yuasa, Kyoto University, Japan Registration Fees: ****************** * Students EU100, regular EU220. Registration will include the proceedings, coffee breaks, the symposium dinner and other amenities. Accommodation is not included.

1 0

[cxml-devel] ELS 2009 in Milan, Italy: Call for Participation
by Marco Antoniotti 15 Apr '09

15 Apr '09

Apologies for multiple postings.... ************************************************************************ 2nd European Lisp Symposium (ELS 2009) Milan, Italy, May 27-29, 2009 Universita` degli Studi di Milano-Bicocca www.european-lisp-symposium.org ************************************************************************ CALL FOR PARTECIPATION ********************** REGISTRATION IS NOW OPEN AT www.european-lisp-symposium.org. Take advantage of the early bird registration fee. Scope and Program Highlights: ***************************** The purpose of the European Lisp Symposium is to provide a forum for the discussion of all aspects of the design, implementation and application of any of the Lisp dialects. We encourage everyone interested in Lisp to participate. The European Lisp Symposium 2009 program includes presentations of high quality papers about novel research results, insights and lessons learned from practical applications, and educational perspectives, all involving Lisp dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, and so on. Kent Pitman will give the keynote address on Thursday, May 28. The presentations will be divided into two categories. * Original contributions. * Work in progress describing ongoing work that will be discussed in the form of a "writers' workshop". The writers' workshops will take place at the symposium in Milan on May 28, 2008. Social Events: ************** Friday 29th evening, Conference Banquet Saturday 30th morning, Guided tour to the "Futurismo" Exhibit in the center of Milan; 2009 marks the 100th anniversary of the Futurism Manifesto; stretching it, the harbinger of Lisp 50 years later. Program Chair: ************** * Antonio Leitao, Technical University of Lisbon, Portugal Local Chair: ************ * Marco Antoniotti, DISCo, Universita`† Milano Bicocca, Italy Program committee: ****************** * Giuseppe Attardi, Universita`† di Pisa , Italy * Pascal Costanza, Vrije Universiteit Brussel, Belgium * Irene Durand, Universite` Bordeaux 1, France * Marc Feeley, Universit` de Montreal, Canada * Ron Garret, Amalgamated Widgets Unlimited, USA * Gregor Kiczales, University of British Columbia, Canada * Scott McKay, ITA Software, Inc., USA * Peter Norvig, Google Inc., USA * Julian Padget, University of Bath, UK * Kent Pitman, PTC, USA * Christian Queinnec, Universite` Pierre et Marie Curie, France * Christophe Rhodes, Goldsmiths College, University of London, UK * Robert Strandh, Universite` Bordeaux 1, France * Mark Tarver, Lambda Associates, UK * Didier Verna, EPITA Research and Development Laboratory, France * JonL White, TheGingerIceCreamFactory of Palo Alto, USA * Taiichi Yuasa, Kyoto University, Japan Registration Fees: ****************** * Early registration before April 25, 2008: Students EU60, regular EU120. * Late registration before May 16, 2008: Students EU80, regular EU160. * Onsite registration: Students EU100, regular EU220. Registration will include the proceedings, coffee breaks, the symposium dinner and other amenities. Accommodation is not included.

1 0

[cxml-devel] Clozure Unicode v.s. cxml-rng
by Ben Hyde 15 Apr '09

15 Apr '09

In clozure code-char returns nil for two ranges: (loop with in = t for i below 1114110 as c = (code-char i) do (cond ((and in (not c)) (setf in nil) (format t "~&gap: #x~X" i)) ((and (not in) c) (setf in t) (format t " .. #x~X" (1- i) )))) gap: #xD800 .. #xDFFF gap: #xFFFE .. #xFFFF NIL Searching on phrases like: "Range: D800–DBFF. The High Surrogate Area does not contain any character" "the value FFFE ! is guaranteed not to be a. Unicode character at all" will throw some additional light on that, and it seems related to this discussion: <http://thread.gmane.org/gmane.lisp.babel.devel/15> These cause the file unicode.lisp in cxml-rng to error when compiling. The following let's it compile; but I doubt this is how anybody who knew what this code was doing would recommend doing this. It reorders the system's components, so I have the range functions from clex available. It then modifies massage-ranges to cut out these gaps from any ranges which pass thru. But my interest is limited to getting the file to compile so my current project, which doesn't need cxml-rng, can get back on track as I experiment with ccl. So I'll admit I haven't tried testing this patch at all. - ben bash-3.2$ git diff diff --git a/cxml-rng.asd b/cxml-rng.asd index e64adff..64582ca 100644 --- a/cxml-rng.asd +++ b/cxml-rng.asd @@ -17,12 +17,12 @@ :components ((:file "package") (:file "floats") + (:file "clex") (:file "unicode") (:file "nppcre") (:file "types") (:file "parse") (:file "validate") (:file "test") - (:file "clex") (:file "compact")) :depends-on (:cxml :cl-ppcre :yacc :parse-number :cl-base64)) diff --git a/unicode.lisp b/unicode.lisp index 42b686a..c5ea17f 100644 --- a/unicode.lisp +++ b/unicode.lisp @@ -57,6 +57,8 @@ `(defranges ,name ',ranges))) (defun massage-ranges (l) + #+ccl (setf l (cxml-clex::ranges- l '((#xd800 #xDFFF) + (#xFFFE #x10000)))) (mapcan (lambda (x) (let ((a (code-char (car x))) (b (code-char (cadr x)))) bash-3.2$

1 0

[cxml-devel] testsuite build fails
by Marco Antoniotti 27 Jan '09

27 Jan '09

Hi this is not CXML per se, but I get the following error while building the test suite. I think it is on the dom2-dtd. Do you have any idea about it? Cheers -- Marco Antoniotti dom2-interfaces: [style] Warning: the task name <style> is deprecated. Use <xslt> instead. [style] Processing /Users/marcoxa/Projects/Lang/CL/cxml/2001/DOM- Test-Suite/lib/specs/Level-2/xml/core/dom-spec.xml to /Users/marcoxa/ Projects/Lang/CL/cxml/2001/DOM-Test-Suite/build/dom2-interfaces.xml [style] Loading stylesheet /Users/marcoxa/Projects/Lang/CL/cxml/ 2001/DOM-Test-Suite/transforms/dom2-combine.xsl [style] : Error! file:/Users/marcoxa/Projects/Lang/CL/cxml/2001/ DOM-Test-Suite/transforms/dom2-combine.xsl: line 137: Attribute 'name' outside of element. [xmlvalidate] /Users/marcoxa/Projects/Lang/CL/cxml/2001/DOM-Test-Suite/ build/dom2-interfaces.xml:417:109: The prefix "xml" cannot be bound to any namespace other than its usual namespace; neither can the namespace for "xml" be bound to any prefix other than "xml". BUILD FAILED /Users/marcoxa/Projects/Lang/CL/cxml/2001/DOM-Test-Suite/build.xml: 1456: Could not validate document /Users/marcoxa/Projects/Lang/CL/cxml/ 2001/DOM-Test-Suite/build/dom2-interfaces.xml

2 1

[cxml-devel] Fwd: [Openmcl-devel] (setf (find-class ...) ...) problem
by Cyrus Harmon 01 Dec '08

01 Dec '08

Pascal's reading of the spec would seem to say that cxml-stp needs an explicit deftype. Thoughts? thanks, cyrus Begin forwarded message: > From: Pascal Costanza <pc(a)p-cos.net> > Date: December 1, 2008 12:20:55 AM PST > To: Cyrus Harmon <ch-openmcl(a)bobobeach.com> > Cc: openmcl-devel Devel <openmcl-devel(a)clozure.com> > Subject: Re: [Openmcl-devel] (setf (find-class ...) ...) problem > > Hi there, > > Section 4.3.1 defines what a proper name of a class is. The > restriction is there because otherwise you could have ambiguities in > the type system. (Two different classes can have the same name, but > only one can have that name as a proper name.) > > > Pascal > > On 1 Dec 2008, at 06:04, Cyrus Harmon wrote: > >> Gary, >> >> Thanks for the thoughtful explanation. Explicitly deftype'ing the >> class first sounds reasonable to me. I've asked the cxml-stp >> developers for their opinion as well. >> >> thanks again, >> >> cyrus >> >> On Nov 30, 2008, at 6:12 PM, Gary Byers wrote: >> >>> >>> >>> On Sun, 30 Nov 2008, Cyrus Harmon wrote: >>> >>>> I'm trying to use david lichteblau's cxml-stp with ccl and am >>>> getting >>>> errors about undefined types. It seems that ccl doesn't like the >>>> following: >>>> >>>> (setf (find-class 'document-type) (find-class 'cxml-stp:document- >>>> type)) >>>> >>> >>> I assume that you mean something like: >>> >>> (defclass fruit () ()) >>> >>> (defclass orange (fruit) ()) >>> >>> (setf (find-class 'tangerine) (find-class 'fruit)) >>> >>> (typep (make-instance 'orange) 'tangerine) complains that TANGERINE >>> isn't a valid type-specifier. >>> >>> My first reaction was to think that that was a bug, but after >>> looking >>> at the spec for a while I haven't yet found anything that confirms >>> that and have found at least one passage that (weakly) contradicts >>> that intuition, but it's a bit unclear. >>> >>> The second paragraph of CLHS 4.3.7 says that "the PROPER name of >>> every class is a valid type specifier.", then discusses the use >>> of class objects as type specifiers and notes TYPE-OF's behavior >>> wrt instances of properly and improperly-named classes. >>> >>> The next paragraph says "Because the names of classes and class >>> objects are type specifiers, they can be used in special form THE >>> and >>> in type declarations." I think that the clearest reading of that is >>> something like "Based on what was established in the preceding >>> paragraph, the PROPER names of classes ... can be used in THE forms >>> and as type specifiers." I'd feel better about making that claim >>> if the language in the third paragraph was a little stronger, but I >>> find it hard to parse the "because" qualifier as referring to >>> anything >>> but what's established in the preceding paragraph. >>> >>> I couldn't find anything else in the spec that was any clearer; the >>> other things that I found referred to things like "symbols naming >>> classes defined by DEFCLASS" and their relation to the type system. >>> (I didn't find anything analogous discussing "symbols established >>> as class names via (SETF FIND-CLASS).") >>> >>> I don't see anything in the spec that says that improper class names >>> -can't- be treated as type specifiers, and it's hard to imagine that >>> anyone's code would break if CCL's (SETF FIND-CLASS) stopped >>> checking >>> for proper-namedness in this case, though it's not quite impossible >>> imagine that. I'm also perfectly willing to believe that there's >>> something else in the spec that's more definitive and that >>> contradicts >>> the interpretation above, but in the absence of that I have to >>> conclude >>> that code that assumes that (SETF (FIND-CLASS a) c) S into a valid >>> type specifier is incorrect (even though it likely "works" in most/ >>> all >>> other implementations.) >>> >>> I think that there actaully are reasons for the spec's (seeming) >>> insistence >>> on only considering properly-named classes to be type specifiers >>> (and >>> that those reasons probably have to do with the compilation model.) >>> I'm >>> not sure that those reasons are fully developed, but I don't think >>> that >>> the spec's distinctions between proper and improper class names are >>> arbitrary and accidental, either. >>> >>> >>> >>> >>> If we all strongly believed that (SETF FIND-CLASS) only made S into >>> a type specifier if S was the class name of C, then a portable way >>> of doing this would be something like: >>> >>> (setf (find-class s) c) >>> (deftype s () 'c) ; whatever the "proper name" of C is >>> >>> CCL actually errs in the expansion of DEFTYPE, because S names a >>> class >>> (even though it doesn't properly name it and even though it's >>> therefore >>> not a type-specifier; it'd be more consistent if the expansion of >>> DEFTYPE >>> did the same kind of check for proper-namedness that (SETF FIND- >>> CLASS) does. >>> >>> It -does- work to do the DEFTYPE first: >>> >>> (deftype tangerine () 'orange) >>> (setf (find-class 'tangerine) (find-class 'orange)) >>> >>> I'm not entirely comfortable in saying that I think that CCL's >>> "right" >>> about this (at least in trying to adhere to the letter of the spec) >>> and >>> that other implementations are all wrong. At the moment, let's just >>> say >>> that I'm not entirely comfortable (though I think that I'd be a >>> little >>> closer to comfort if CCL was more consistent, e.g., if DEFTYPE's >>> expansion >>> only rejected attempts to redefine class-names that the >>> implementation >>> considered to be type specifiers.) >>> >>> >>> >>> >>> >>> >>> >>> >>> >>>> a similar problem was discussed a while back where this problem >>>> arose >>>> with GSharp, but I'm not sure what the resolution was. Any >>>> suggestions? >>>> >>>> thanks, >>>> >>>> Cyrus >>>> >>>> _______________________________________________ >>>> Openmcl-devel mailing list >>>> Openmcl-devel(a)clozure.com >>>> http://clozure.com/mailman/listinfo/openmcl-devel >>>> >>>> >> >> _______________________________________________ >> Openmcl-devel mailing list >> Openmcl-devel(a)clozure.com >> http://clozure.com/mailman/listinfo/openmcl-devel > > -- > Pascal Costanza, mailto:pc@p-cos.net, http://p-cos.net > Vrije Universiteit Brussel, Programming Technology Lab > Pleinlaan 2, B-1050 Brussel, Belgium > > > > > > > >

1 0

[cxml-devel] cxml-stp patch for ccl
by Cyrus Harmon 01 Dec '08

01 Dec '08

the following patch allows cxml-stp to compile under ccl: diff --git a/classes.lisp b/classes.lisp index 026cfc3..db70b47 100644 --- a/classes.lisp +++ b/classes.lisp @@ -86,6 +86,9 @@ @see-slot{system-id} @see-slot{public-id} @see-slot{internal-subset}")) +#+ccl +(deftype document-type () 'cxml-stp:document-type) + (setf (find-class 'document-type) (find-class 'cxml-stp:document- type)) (defclass cxml-stp:document (parent-node) () The problem is that (setf (find-class ...) ...) doesn't create the type under ccl. Arguably, this shouldn't be necessary. But, as Gary Byers has pointed out on openmcl-devel, that point is arguable and he makes a decent case as to why this shouldn't work. thoughts? thanks, Cyrus

1 0

[cxml-devel] closure-common fix to work with simple-base-string's
by Attila Lendvai 20 Nov '08

20 Nov '08

dear list, please find a patch attached that fixes a problem that (subtypep 'simple-base-string '(simple-array character (*))) NIL T therefore string-rod needs to make new simple-array's to keep the rest of the codebase happy. -- attila

1 1

[cxml-devel] Problems compiling Xuriella
by Chaitanya Gupta 19 Nov '08

19 Nov '08

Hi, I have encountered a few problems while compiling Xuriella on both Allegro CL and SBCL. On compiling Xuriella on ACL, I get the following warnings: Warning: While compiling these undefined functions were referenced: (SETF XURIELLA::TEMPLATE-MODE) from position 50393 in /home/chaitanya/lisp/libs/site/xuriella/dev/xslt.lisp (SETF XURIELLA::TEMPLATE-BASE-URI) from position 50393 in /home/chaitanya/lisp/libs/site/xuriella/dev/xslt.lisp (SETF XURIELLA::TEMPLATE-STYLESHEET) from position 50393 in /home/chaitanya/lisp/libs/site/xuriella/dev/xslt.lisp (SETF XURIELLA::SINK-ELEMENT-USED-PREFIXES) from position 4861 in /home/chaitanya/lisp/libs/site/xuriella/dev/unparse.lisp (SETF XURIELLA::SINK-ELEMENT-ACTUAL-QNAME) from position 3094 in /home/chaitanya/lisp/libs/site/xuriella/dev/unparse.lisp XURIELLA::*UNPARSE-XML-COUNTER* from position 2860 in /home/chaitanya/lisp/libs/site/xuriella/dev/unparse.lisp, 7305 in /home/chaitanya/lisp/libs/site/xuriella/dev/unparse.lisp, 10553 in /home/chaitanya/lisp/libs/site/xuriella/dev/unparse.lisp, 11725 in /home/chaitanya/lisp/libs/site/xuriella/dev/unparse.lisp The first five warnings (SETF XURIELLA::...) all seem to be related to ACL using defsetf instead of setf functions for structure slots. This has been discussed before on the list too [1]. The last issue (XURIELLA::*UNPARSE-XML-COUNTER*) causes problems on both ACL and SBCL. This, to me, seems because the WITH-PROFILE-COUNTER macro is defined in xslt.lisp whereas it is also used in unparse.lisp, which is loaded before xslt.lisp. Chaitanya 1. http://common-lisp.net/pipermail/cxml-devel/2008-July/000437.html

1 1

[cxml-devel] reading an ignored variable
by Cyrus Harmon 06 Nov '08

06 Nov '08

the following patch fixes a warning about reading an ignored variable. thanks, cyrus diff --git a/xml/xmlns-normalizer.lisp b/xml/xmlns-normalizer.lisp index b4f4444..06f03e2 100644 --- a/xml/xmlns-normalizer.lisp +++ b/xml/xmlns-normalizer.lisp @@ -131,6 +131,5 @@ (sax:start-element (proxy-chained-handler handler) uri lname qname attrs)) (defmethod sax:end-element ((handler namespace-normalizer) uri lname qname) - (declare (ignore qname)) (pop (xmlns-stack handler)) (sax:end-element (proxy-chained-handler handler) (or uri #"") lname qname))

1 0

[cxml-devel] SAX handler
by Andy Chambers 10 Sep '08

10 Sep '08

Hi, What is the current recommended method of implementing a custom SAX handler? The documentation says that you just need to implement the generic functions for any old class but when you do that, you get lots of warnings like the following. "deprecated SAX default method used by a handler that is not a subclass of SAX:ABSTRACT-HANDLER or HAX:ABSTRACT-HANDLER" Should new code inherit from sax:default-handler? Cheers, Andy

2 1

[cxml-devel] CXML performance
by Chaitanya Gupta 10 Sep '08

10 Sep '08

Hi, I tried using CXML to parse a slightly big (~1.2 MB) XML in ACL 8.0. I am using the following form to parse it into a DOM: (cxml:parse xml (cxml-dom:make-dom-builder)) ; xml is a string Generally, it takes about 0.73-0.75 sec to parse on my machine. What also happens is that, while the parser is running, it blocks all the other threads i.e. they become unresponsive. Any clues on why it can be happening? And how it can be fixed? Also, ACL on OS X (and Linux) does not run any Lisp code while a foreign call is being made (thus blocking all the other threads). Is there any chance that CXML calls any foreign code? Chaitanya

3 5

[cxml-devel] Fwd: Problem with cxml-xmls:map-node?
by Daniel Katz 19 Aug '08

19 Aug '08

Hi - I'm exploring cxml, and I'm running into trouble using the cxml- xmls:map-node. I don't know whether I'm doing something stupid or whether it's a bug, so I thought I'd ask here. I began by following the example in the Quick-Start Guide (http:// common-lisp.net/project/cxml/quickstart.html#id54132) and found myself in the debugger with an error related to namespaces: > > CL-USER> (with-open-file (out > "example.out" :direction :output :element-type '(unsigned-byte 8)) > (cxml-xmls:map-node (cxml:make-character-stream- > sink out) > '("test" (("a" "b")) > ("child" nil)))) > > serializing with :INCLUDE-NAMESPACE-URI, but node was created > without namespace URI > [Condition of type SIMPLE-ERROR] > > Restarts: > 0: [ABORT] Return to SLIME's top level. > 1: [ABORT-BREAK] Reset this process > 2: [ABORT] Kill this process > > Backtrace: > 0: ((:INTERNAL CXML-XMLS::WALK CXML-XMLS::MAP-NODE/LNAMES) > '("test" (("a" "b")) ("child" NIL))) > 1: (CXML-XMLS::MAP-NODE/LNAMES #<CXML::NAMESPACE-NORMALIZER > #x8D0290E> '("test" (("a" "b")) ("child" NIL)) 'T) > 2: (#<Anonymous Function #x8D04486>) I have to admit that I didn't find this error to be very useful in terms of understanding what the problem is. My second attempt was to avoid constructing the xmls-style data by hand but to instead take the output of a cxml parse. Suffice it to say that I ran into the same issue: > CL-USER> (with-open-file (out "foo.out" :direction :output :element- > type '(unsigned-byte 8)) > (cxml-xmls:map-node (cxml:make-character-stream- > sink out) > (cxml:parse-file > "foo.xml" (cxml-xmls:make-xmls-builder)))) > > > serializing with :INCLUDE-NAMESPACE-URI, but node was created > without namespace URI > [Condition of type SIMPLE-ERROR] > > Restarts: > 0: [ABORT] Return to SLIME's top level. > 1: [ABORT-BREAK] Reset this process > 2: [ABORT] Kill this process > > Backtrace: > 0: ((:INTERNAL CXML-XMLS::WALK CXML-XMLS::MAP-NODE/LNAMES) > '("foo" NIL " > " > ("bar" (("quux" "quux")) " > baz > ") > " > ")) > 1: (CXML-XMLS::MAP-NODE/LNAMES #<CXML::NAMESPACE-NORMALIZER > #x8CFCF86> '("foo" NIL " > " > ("bar" (("quux" "quux")) " > baz > ") > " > ") 'T) > 2: (#<Anonymous Function #x8C7D31E>) > 3: (SWANK::EVAL-REGION "(with-open-file (out \"foo.out\" > :direction :output > :element-type '(unsigned-byte 8)) > (cxml-xmls:map-node (cxml:make-character-stream-sink out) > (cxml:parse-file \"foo.xml\" (cxml-xmls:make-xmls- > builder)))) > ") So now I'm sort of at a loss for what to do next. And my basic question once again is: am I doing something stupid? Or is the xmls- style serialization facility broken? Thanks. Dan

1 1

[cxml-devel] Bug in validating XSD:DATE
by Chaitanya Gupta 18 Aug '08

18 Aug '08

If I have an RNC file which looks like this: start = element foo { element bar { text }, element baz { xsd:date } } and try to validate against this schema an XML which looks like this: <foo> <bar>haha!</bar> <baz>2008-09-09T22:00:00</baz> </foo> (Note that the value of 'baz' should have been a date, not a date-time) I get the following error/backtrace: `NIL' is not of the expected type `NUMBER' [Condition of type TYPE-ERROR] Restarts: 0: [ABORT-REQUEST] Abort handling SLIME request. 1: [ABORT] Abort entirely from this (lisp) process. Backtrace: 0: (SWANK::DEBUG-IN-EMACS #<TYPE-ERROR @ #x117dba9a>) 1: (SWANK:SWANK-DEBUGGER-HOOK #<TYPE-ERROR @ #x117dba9a> #<Function SWANK-DEBUGGER-HOOK>) 2: (ERROR TYPE-ERROR :DATUM NIL :EXPECTED-TYPE NUMBER :FORMAT-CONTROL "~@<`~s' is not of the expected type `~s'~:@>" :FORMAT-ARGUMENTS (NIL NUMBER)) 3: (CXML-TYPES::PARSE-TIME NIL NIL NIL NIL #1="0" #1# #1# NIL NIL ...) 4: ((METHOD CXML-TYPES::PARSE/XSD (CXML-TYPES:DATE-TYPE T T)) #<CXML-TYPES:DATE-TYPE > "2008-09-09T22:00:00" #<CXML-RNG::VALIDATOR @ #x117cb302>) 5: ((METHOD CXML-TYPES::PARSE/XSD :AROUND (CXML-TYPES:XSD-TYPE T T)) #<CXML-TYPES:DATE-TYPE > "2008-09-09T22:00:00" #<CXML-RNG::VALIDATOR @ #x117cb302>) 6: ((:INTERNAL (:EFFECTIVE-METHOD 3 NIL NIL T T) 0) #<CXML-TYPES:DATE-TYPE > "2008-09-09T22:00:00" #<CXML-RNG::VALIDATOR @ #x117cb302>) 7: ((METHOD CXML-TYPES:VALIDP (CXML-TYPES:XSD-TYPE T)) #<CXML-TYPES:DATE-TYPE > "2008-09-09T22:00:00" #<CXML-RNG::VALIDATOR @ #x117cb302>) 8: ((METHOD CXML-RNG::|DATA'| (T CXML-RNG:DATA T)) #<CXML-RNG::VALIDATOR @ #x117cb302> #<CXML-RNG:DATA @ #x117c65a2> "2008-09-09T22:00:00") Attached is a patch which fixes this. Now I get the expected error: text node not valid, was expecting a text node of type #<DATE-TYPE > [ Error at line 3, column 33 in #<PURI:URI file://+/Users/chaitanya/tmp/test.xml> ] [Condition of type CXML-RNG:RNG-ERROR] On a side note, I think that the error reporting can be improved a bit. e.g. the element inside which the validation error was encountered, can that also be reported? Chaitanya diff --git a/types.lisp b/types.lisp index 26f89fa..1d481c6 100644 --- a/types.lisp +++ b/types.lisp @@ -1049,11 +1049,11 @@ (num (str) (and str (parse-number:parse-number str)))) (setf (values y m d h min s tz-h tz-m) - (values (* (int y) (if minusp -1 1)) + (values (and y (* (int y) (if minusp -1 1))) (int m) (int d) (int h) (int min) (num s) (int tz-h) (int tz-m)))) - (let ((day-limit (day-limit m y))) + (let ((day-limit (and m y (day-limit m y)))) ;; check ranges (cond ((and y m d h min s

1 0

[cxml-devel] Problem compiling PARSE-SCHEMA on ACL
by Chaitanya Gupta 18 Aug '08

18 Aug '08

Hi, When I try to call PARSE-SCHEMA in ACL, I get this error -- attempt to call the undefined function (SETF CXML-RNG::GRAMMAR-START) with args: #S(CXML-RNG::DEFINITION :NAME :START :COMBINE-METHOD NIL :HEAD-P NIL :REDEFINITION NIL :CHILD ...) #S(CXML-RNG::GRAMMAR :START NIL :PARENT NIL :DEFINITIONS #<EQUAL hash-table with 0 entries @ #x13904c62>). [Condition of type UNDEFINED-FUNCTION] This happens because GRAMMAR is defined after PARSE-SCHEMA in parse.lisp. Same issue with the DEFN-CHILD accessor for DEFINITION. If I move the definition of PARSE-SCHEMA to the end of the file, for example, the issue is fixed. Chaitanya

2 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cxml-devel