http://blog.gmane.org/gmane.lisp.interpol.general hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.lisp.interpol.general/18 <pre>Thank you for contacting me. ASM _______________________________________________ cl-interpol-devel site list cl-interpol-devel&lt; at &gt;common-lisp.net http://common-lisp.net/mailman/listinfo/cl-interpol-devel</pre> Anthony Martin 2012-05-02T01:18:30 http://comments.gmane.org/gmane.lisp.interpol.general/12 <pre>Dear cl-interpol developer(s), I would like to use cl-interpol to parse strings containing Perl subpattern variables like $1 and Makefile special variables like $&lt;, $^ etc. I also want statements like #?"$(f 5)" when *optional-delimiters-p* is t to be expanded into something like (with-output-to-string (#:string) (princ (f 5) #:string)) rather than (with-output-to-string (#:string) (princ (progn f 5) #:string)) as they do now. (However, for better compatibility with Makefiles I need to treat the case of the list made of a single element in a special way, expanding it to the value of the corresponding variable.) Overall, I would like to have better control over the read-form function, maybe the possibility to supply my own one. Could you install some hook there? I'd gladly do it myself and send you a patch but I'm not sure which way is the best and whether you will accept such a change at all. If you advice me some workaround that doesn't involve modifying cl-interpol it would also be great. I just don't want to fork or recreate the whole library because of a single function. _______________________________________________ cl-interpol-devel site list cl-interpol-devel&lt; at &gt;common-lisp.net http://common-lisp.net/mailman/listinfo/cl-interpol-devel </pre> Evgeniy Zhemchugov 2009-12-16T15:00:51 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.lisp.interpol.general