Hello again :)
On Mon 11 Apr 2011 15:08, Wolfgang J Moeller writes:
> Having any sort of escapes mixed with #{ }# notation would be incompatible -
> maybe you ought no longer generate #{ }# on output, but switch to R6RS escapes
> throughout. Since there has been (in my understanding) no way to r
Hi,
On Mon 11 Apr 2011 14:23, Wolfgang J Moeller writes:
> Subsequently I noticed that `psyntax-pp.scm' is full of symbols
> #{name\ number}# which so far, would _not_ be read in
> as the original "gensym"s.
>
> This is going to change if you re-generate `psyntax-pp.scm'
> using the "fixed" GUIL
On Mon, 11 Apr 2011, Andy Wingo wrote:
>[...]
> > (*) Apparently, reading a "weird" symbol whose name contains "}#"
> > isn't provided for.
>
> Also; irritating. Relatedly it does not seem that Guile supports R6RS
> hex escapes in symbols. I guess the right thing to do is to allow for
> R6RS
On Mon, 11 Apr 2011, Andy Wingo wrote:
> On Tue 05 Apr 2011 17:27, Wolfgang J Moeller writes:
>
> > scm_i_print_symbol_name() in libguile/print.c ought not insert backslashes
> > into "weird" symbol names that it prints using #{ ... }#,
> > because the "e
Hi Wolfgang,
On Tue 05 Apr 2011 17:27, Wolfgang J Moeller writes:
> scm_i_print_symbol_name() in libguile/print.c ought not insert backslashes
> into "weird" symbol names that it prints using #{ ... }#,
> because the "extended read syntax" (in agreement with the d
On Tue 05 Apr 2011 17:27, Wolfgang J Moeller writes:
> scm_i_print_symbol_name() in libguile/print.c ought not insert backslashes
> into "weird" symbol names that it prints using #{ ... }#,
> because the "extended read syntax" (in agreement with the documentation
scm_i_print_symbol_name() in libguile/print.c ought not insert backslashes
into "weird" symbol names that it prints using #{ ... }#,
because the "extended read syntax" (in agreement with the documentation)
doesn't treat backslashes specially, nor _usually_ needs escapin
