Hi, Moritz--
On Thu, Aug 22, 2013 at 3:01 PM, Moritz Heidkamp
wrote:
> (use sxml-transforms)
> (define some-data '(some #\d (#\a "ta")))
> (SRV:send-reply (pre-post-order some-data) universal-conversion-rules))
Thanks for the suggestion. I'm now working on this.
> the deal with that name
Hi Matt,
Matt Gushee writes:
> markdown->sxml converts whitespace in the input to character objects,
> or lists of character objects, e.g.:
>
>'(#\space)
>#\newline
>
> ... but serialize-sxml can't handle these: evidently it wants either
> strings or symbols. I haven't found any arguments
Hi, Jim--
On Wed, Aug 21, 2013 at 10:12 PM, Jim Ursetto wrote:
> I don't remember offhand what the rationale was for this in sxml-serializer
> -- I can take a look but it might not be until this weekend.
Sounds good. I was actually hoping to be able to blame lowdown for
this, since I don't real
On Thu, Aug 22, 2013 at 6:39 PM, John Cowan wrote:
> Michele La Monaca scripsit:
>
>> I think eval usage (and limitations) can be avoided: For example:
>>
>> (define-syntax eping
>> (syntax-rules ()
>> ((_ h)
>> (handle-exceptions exn
>>(_eping (symbol->string '|h|))
>>(
[ Today is the last day of early registration. ]
==
==
CALL FOR PARTICIPATION
18th ACM SIGPLAN International Conference on Functional Programming
ICFP 2013
Boston, MA, USA, 25-27 September 2013
Affiliated events 22-24 September
Hello,
Please, find below the second call for papers for PEPM 2014.
Please forward these to anyone you think may be interested.
Apologies for any duplicates you may receive.
best regards,
Jurriaan Hage
Co-chair of PEPM 2014
-
Michele La Monaca scripsit:
> I think eval usage (and limitations) can be avoided: For example:
>
> (define-syntax eping
> (syntax-rules ()
> ((_ h)
> (handle-exceptions exn
>(_eping (symbol->string '|h|))
>(let ((t h)) (_eping t))
That traps all exceptions, not ju
On Thu, Aug 22, 2013 at 4:54 PM, John Cowan wrote:
> Your macro will work as far as handling bound and unbound symbols; of
> course, symbols *lexically* bound will not be seen, only global symbols.
> That's the nature of Scheme's eval.
I think eval usage (and limitations) can be avoided: For exa
On 08/22/13 10:54:44, John Cowan wrote:
> Like your earlier macro that attempts to remap h to |h|, this one
> won't
> quite work, because the difference between h and |h| disappears in
> the
> reader, and the macro engine never sees it. 192.168.0.1 is simply
> not
> valid Scheme lexical syntax,
Michele La Monaca scripsit:
> How can I check if a symbol is bound to a value?
By using eval and trapping any error, as you mention below, but that's
not to the purpose here. You are trying to do with macros what macros
cannot do.
> (define-syntax eping
> (syntax-rules ()
> ((_ h)
>
How can I check if a symbol is bound to a value?
I would like to do this:
(define host "example.com")
(eping host) ; host is evaluated
(eping localhost) ; localhost is treated as a symbol
with a macro like that:
(define-syntax eping
(syntax-rules ()
((_ h)
(if (and (symbol? 'h)
Forget the previous macro. Hopefully this one will do the intended job.
(define-syntax eping
(syntax-rules ()
((_ h)
(_eping (symbol->string '|h|)))
((_ h p1 p2 ...) (_eping (symbol->string '|h|) 'p1 p2 ...
On Thu, Aug 22, 2013 at 11:29 AM, Michele La Monaca
wrote:
> On Wed,
On Wed, Jun 26, 2013 at 2:22 PM, John Cowan wrote:
> Michele La Monaca scripsit:
>
>> Happy pinging.
>
> Cool!
>
> I made a minor documentation change on the wiki to encourage strings over
> symbols as hostnames, and to remove the suggestion to use dotted-decimal
> symbols like '192.168.1.1. Such
13 matches
Mail list logo
