Re: Unrecognized \ sequences and Elisp

[Marius Vollmer]

Neil Jerram <address@hidden> writes:

>     Marius> What about having 'elisp-strings' instead
>     Marius> escaped-parens?  Escaped-parens seems very, very
>     Marius> specific to me but still its only use is to allow the
>     Marius> reading of elisp strings.
>
> OK, I'll make this change.

Thanks!

>     Marius> In the long run, I think we should have a configurable
>     Marius> reader, much like Common Lisp specifies it.
>
> Can you give a reference?

Here: http://www.lispworks.com/reference/HyperSpec/Body/02_aa.htm

>     Marius> It is a good thing to do, but i this case, not strictly
>     Marius> necessary, I'd say.  You could also have renamed
>     Marius> scm_lreadparen to scm_i_lreadparen (or made it static,
>     Marius> maybe) and thus removed it from the public interface of
>     Marius> libguile.
>
> So ...
>
> (1) In this case, should I simplify my change by:
>
>     - eliminating scm_lreadparen (as it is now)
>
>     - renaming scm_lreadparen1 to scm_lreadparen
>
>     - making scm_lreadparen static?

Yes.

> (2) In general, how do users know what in the C API we are trying to
>     preserve?  (I think the answer should be "whatever is documented
>     in the manual", but currently that probably doesn't cover enough.)

There is a naming convention: everything starting with "scm_i_" is
internal.  But not everything that shuld be internal has been marked
this way yet...

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405