[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> Agreed, but that's only the name of the Info node. Changing it here
> would make the line too long for Info.
Call the node just "Internationalization" and then call the sub nodes
something else, that should fit fine. There's a good chance people
co
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
> what is the status of the eval options structure wrt binary compatibility?
I remeber now: changing the size of a data object in a shared library
breaks mainlines using it, or even just taking its address. And both
mainline and the library are broke
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
> As such, it does not conform to the GUILE naming standards.
Where? string-move! is the same, and copy-file is similar.
In any case as I said it can't be changed, but if you think the docs
are unclear then propose new words or a sentence of caution
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
> Perhaps, but I'm for cleaner code. Having to keep deprecated stuff
> around (and worse: having to write various deprecation wrappers for
> them) is detrimental to code quality.
I would say the contrary is worse. Users following the advertised
rules
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> [EMAIL PROTECTED] {Scheme Procedure} locale-yes-regexp [locale]
> [EMAIL PROTECTED] {Scheme Procedure} locale-no-regexp [locale]
> +Return a string that can be used as a regular expression to recognize
> +a positive (respectively, negative) response t
Kevin Ryde escreveu:
> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>> As such, it does not conform to the GUILE naming standards.
>
> Where? string-move! is the same, and copy-file is similar.
I was previously told that functions that carry a ! in their name
modify their first argument.
--
