Re: [racket-users] ssax:make-parser

2018-05-19 Thread N. Raghavendra
At 2018-05-16T23:47:29+05:30, N. Raghavendra wrote: > At 2018-05-16T13:49:52-04:00, John Clements wrote: > >> Would you (N. Raghavendra) be interested in taking the raw >> pseudo-documentation currently provided for ssax:make-parser and >> reformatting it into something useful, perhaps with an

Re: [racket-users] ssax:make-parser

2018-05-17 Thread Neil Van Dyke
N. Raghavendra wrote on 05/17/2018 03:29 PM: I think 3 is the most attractive possibility, Agreed.  #1 and #2 are for gracefully handling backward compatibility, and for accommodating a decentralized volunteer model. One way that #2 is volunteer-friendly is that, I suggest, for example,

Re: [racket-users] ssax:make-parser

2018-05-17 Thread N. Raghavendra
At 2018-05-17T13:40:47-04:00, Neil Van Dyke wrote: > One strategy for SXML-related support would be for the Racket > community to collectively do all 3 of these: > > 1. Treat the monolithic `sxml` package of Oleg's various SXML-related > tools remaining pretty frozen in its current state. This

Re: [racket-users] ssax:make-parser

2018-05-17 Thread N. Raghavendra
At 2018-05-17T12:45:50-04:00, John Clements wrote: > Honestly, reading that snippet … suggests to me that make-parser might > not actually be useful without all of the other internal ssax > functions, and that perhaps make-parser really shouldn’t be exported, > after all :). If you wish, pending

Re: [racket-users] ssax:make-parser

2018-05-17 Thread Neil Van Dyke
One strategy for SXML-related support would be for the Racket community to collectively do all 3 of these: 1. Treat the monolithic `sxml` package of Oleg's various SXML-related tools remaining pretty frozen in its current state. This will be the "raw, classic, everything" package.  It will be

Re: [racket-users] ssax:make-parser

2018-05-17 Thread 'John Clements' via Racket Users
Honestly, reading that snippet … suggests to me that make-parser might not actually be useful without all of the other internal ssax functions, and that perhaps make-parser really shouldn’t be exported, after all :). Is it possible to formulate productive uses of make-parser that don’t require

Re: [racket-users] ssax:make-parser

2018-05-17 Thread N. Raghavendra
At 2018-05-16T14:56:00-04:00, John Clements wrote: > In a quick scan of the existing quasi-documentation for ssax.rkt, > make-parser was the only one that looked to me like it might > productively be used from outside. `ssax:read-pi-body-as-string' is another identifier from sxml/ssax/ssax,

Re: [racket-users] ssax:make-parser

2018-05-16 Thread Neil Van Dyke
John Clements, et al., thank you for ongoing work on packaging Oleg Kiselyov's SXML-related libraries nicely for Racket.  It's not an easy task. (Background, for the list... Years ago, one of the great masters of Scheme, Oleg Kiselyov, did a lot of excellent work on XML in Scheme, released

Re: [racket-users] ssax:make-parser

2018-05-16 Thread N. Raghavendra
At 2018-05-16T14:56:00-04:00, John Clements wrote: > Maybe… I’m inclined to respect Ryan’s thinking on this; there are a > bunch of functions in there that look like they definitely shouldn’t > be exposed, and couldn’t reasonably be called from outside. In a quick > scan of the existing

Re: [racket-users] ssax:make-parser

2018-05-16 Thread 'John Clements' via Racket Users
> On May 16, 2018, at 11:17 AM, N. Raghavendra wrote: > > At 2018-05-16T13:49:52-04:00, John Clements wrote: > >> It seems like make-parser should probably be provide’d. I’ve pushed a >> change to make ssax:make-parser a top-level provide. > > Thank you very much. In

Re: [racket-users] ssax:make-parser

2018-05-16 Thread N. Raghavendra
At 2018-05-16T13:49:52-04:00, John Clements wrote: > It seems like make-parser should probably be provide’d. I’ve pushed a > change to make ssax:make-parser a top-level provide. Thank you very much. In fact, it may be a good idea to restore (provide (all-from-out "ssax/ssax.rkt")) > Would you

Re: [racket-users] ssax:make-parser

2018-05-16 Thread 'John Clements' via Racket Users
It seems like make-parser should probably be provide’d. I’ve pushed a change to make ssax:make-parser a top-level provide. Would you (N. Raghavendra) be interested in taking the raw pseudo-documentation currently provided for ssax:make-parser and reformatting it into something useful, perhaps

Re: [racket-users] ssax:make-parser

2018-05-16 Thread Ryan Culpepper
On 05/15/2018 11:36 PM, John Clements wrote: Interestingly, it looks like this change is a deliberate one, made by Ryan Culpepper back in 2011. Here’s the relevant commit: commit 738bf41d106f4ecd9111bbefabfd78bec8dc2202 Author: Ryan Culpepper Date: Tue Nov 22 02:46:32

Re: [racket-users] ssax:make-parser

2018-05-15 Thread N. Raghavendra
At 2018-05-15T17:36:44-04:00, John Clements wrote: > Interestingly, it looks like this change is a deliberate one, made by > Ryan Culpepper back in 2011. Here’s the relevant commit: Thanks for tracing that change. Raghu. -- N. Raghavendra , http://www.retrotexts.net/

Re: [racket-users] ssax:make-parser

2018-05-15 Thread 'John Clements' via Racket Users
Interestingly, it looks like this change is a deliberate one, made by Ryan Culpepper back in 2011. Here’s the relevant commit: commit 738bf41d106f4ecd9111bbefabfd78bec8dc2202 Author: Ryan Culpepper Date: Tue Nov 22 02:46:32 2011 -0700 bypass ssax/ssax module