[Chicken-users] ssax troubles
I'm trying to work with the ssax module, but no matter what I do, I get the following error: Error: unbound variable: ssax:scan-Misc Call history: ##sys#require tagnuke.scm:4: open-input-file tagnuke.scm:21: outline scan-for-significant-prolog-token-1524543 ssax:scan-Misc -- This is basically identical to the issue described here: http://lists.nongnu.org/archive/html/chicken-users/2009-10/msg00070.html In that thread, the maintainer (I assume) of the ssax egg offers a patch to the ssax-chicken.scm file, but that patch doesn't seem to have made it into the ssax egg itself (though I'm not sure how to verify that, since I can't seem to figure out how to grab the source for an egg and install it manually). I guess my broader question is: Is ssax busted? I'm basically trying to do the same thing as the person in the earlier thread (i.e. run some example code). Steve -- Stephen Ramsay Associate Professor Department of English Center for Digital Research in the Humanities University of Nebraska-Lincoln PGP Public Key ID: 0xA38D7B11 http://lenz.unl.edu/ ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] ssax troubles
On Sun, Feb 19, 2012 at 10:16:50AM -0600, sramsay@gmail.com wrote: This is basically identical to the issue described here: http://lists.nongnu.org/archive/html/chicken-users/2009-10/msg00070.html In that thread, the maintainer (I assume) of the ssax egg offers a patch to the ssax-chicken.scm file, but that patch doesn't seem to have made it into the ssax egg itself I'm not the maintainer of ssax. Actually, it has no official maintainer, it's more or less a community effort :) I guess this fix slipped through the cracks. Anyway, I've applied the patch by Taylor to the trunk version and pushed a new 5.0.6 release which should appear shortly. Thanks for reporting the bug (again)! (though I'm not sure how to verify that, since I can't seem to figure out how to grab the source for an egg and install it manually). Unless otherwise stated on the egg's wiki page, most eggs are kept in the eggs repository in subversion. You can check this out via https://code.call-cc.org/svn/chicken-eggs/release/4/ssax/trunk If you have no account, you can use the anonymous username with an empty password to get read-only access. This information can also be found on http://code.call-cc.org/ which is linked from the wiki and the main site. I guess my broader question is: Is ssax busted? I'm basically trying to do the same thing as the person in the earlier thread (i.e. run some example code). It's not really busted; it's just not as well-maintained as most other eggs. Cheers, Peter -- http://sjamaan.ath.cx -- The process of preparing programs for a digital computer is especially attractive, not only because it can be economically and scientifically rewarding, but also because it can be an aesthetic experience much like composing poetry or music. -- Donald Knuth ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] ssax troubles
Peter Bex peter@xs4all.nl writes: Unless otherwise stated on the egg's wiki page, most eggs are kept in the eggs repository in subversion. You can check this out via https://code.call-cc.org/svn/chicken-eggs/release/4/ssax/trunk If you have no account, you can use the anonymous username with an empty password to get read-only access. Another way to get an egg's source is through `chicken-install -r` which also works for eggs which aren't kept in the subversion egg repository. Moritz ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] ssax troubles
On 19 February 2012 at 17:43, Peter Bex peter@xs4all.nlwrote: I'm not the maintainer of ssax. Actually, it has no official maintainer, it's more or less a community effort :) I guess this fix slipped through the cracks. Anyway, I've applied the patch by Taylor to the trunk version and pushed a new 5.0.6 release which should appear shortly. Wow. Talk about service! I'm coming back to chicken after a long hiatus, and still trying to get my bearings. I imagine it will be a while before I can join the community's effort to maintain ssax, but it may come to that. ;) I do text analysis stuff, and most of the stuff is (for better or for worse) in XML. So thanks, and thanks to Moritz for the tip on how to get the source through chicken-install. Steve -- Stephen Ramsay Associate Professor Department of English Center for Digital Research in the Humanities University of Nebraska-Lincoln PGP Public Key ID: 0xA38D7B11 http://lenz.unl.edu/ ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] ssax troubles
On 19 February 2012 at 17:43, Peter Bex peter@xs4all.nlwrote: Anyway, I've applied the patch by Taylor to the trunk version and pushed a new 5.0.6 release which should appear shortly. Getting closer . . . ;) It's now complaining about: Error: unbound variable: nl Call history: ##sys#require tagnuke.scm:4: open-input-file tagnuke.scm:21: outline scan-for-significant-prolog-token-1524543 ssax#ssax:scan-Misc ssax#ssax:warn -- And this one looks pretty straightforward. The warn function in ssax-chicken.scm: (define (ssax:warn port msg . other-msg) (apply cerr (cons* nl Warning: msg other-msg)) is calling nl, which is defined in myenv-chicken.scm (it's just an alias for (string #\newline). But myenv-chicken.scm isn't included until after that definition. Or so it seems to me. I'd send a patch, but I have a feeling you don't want a noob messing around with this, and I assume I don't have the ability to put patched code back into the egg repository. Any chance of a quick fix? Steve -- Stephen Ramsay Associate Professor Department of English Center for Digital Research in the Humanities University of Nebraska-Lincoln PGP Public Key ID: 0xA38D7B11 http://lenz.unl.edu/ ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
