Greetings all,
You might know Andreas Rottman from such commits as
cb65f76c7408569d72ed82b77a154acd79d29c69, or even of
ead04a04cd38909d0d40f1ba7885372c9c65ff38.
I'm pleased to note that we finally gave him the keys to the Guile
castle. I'm sure we'll shortly see him working on the hygienic
foun
Andy Wingo writes:
> Have patience :) We will get there in time. The process of
> consensus-building is work. This is a very important decision to make,
> and its engineering implications are large. We've only been discussing
> it for a week :)
Words of wisdom, to be sure. For what it's wort
Andy Wingo writes:
> I am quite sensitive to the "justice" argument -- that we not restrict
> the names our users give to Scheme identifiers, or the characters they
> use in their strings. But these values typically come from literals in
> C source code, which has no portable superset of ASCII.
I've been following the development of Guile for years, and firstly
congratulations on Guile 2.0. It really is a masterpiece.
Amongst other things, I quite enjoy using ",disassemble" to see what the
VM generation is doing, but maybe I shouldn't go on too much about my
hobbies. Anyhow, I notice
Noah Lavine writes:
> I think there are two questions being conflated here: what Guile's
> internal string representation should be, and what convenience
> functions should be provided for users to easily make symbols.
Yes, you are absolutely right. They are two separate questions. They
were cl
Hello!
I have been sitting in the sun pondering all this for an hour or so now,
and there is a lot to say, I think. But we should get this out of the
way first:
On Sat 19 Mar 2011 15:06, Mark H Weaver writes:
> As a meta-comment: I've grown rather weary from fighting this battle
> alone. My h
Hello all,
>> Furthermore, such a default would not restrict our users at all -- they
>> can always use the non-_c_ variants with a symbol explicitly constructed
>> with (e.g.) scm_from_utf8_symbol.
>
> We have those convenience functions for a reason. You recently proposed
> several more conveni
Andy Wingo writes:
>> Ludovic, Andy and I discussed this on IRC, and came to the conclusion
>> that UTF-8 should be the encoding assumed by functions such as
>> scm_c_define, scm_c_define_gsubr, scm_c_define_gsubr_with_generic,
>> scm_c_export, scm_c_define_module, scm_c_resolve_module,
>> scm_c_u
On Tue 15 Mar 2011 16:46, Mark H Weaver writes:
> I'd also like to point out that the R6RS is the only relevant standard
> that mandates O(1) string accessors. The R5RS did not require this, and
> WG1 for the R7RS has already voted against this requirement.
>
> http://trac.sacrideo.us/wg/ticke
Hello Guilers,
GNU was accepted into the Google Summer of Code. Sweet!
The timeline, again, is here:
http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline
In particular:
March 18:
List of accepted mentoring organizations published on the Google
Greetings,
On Wed 16 Mar 2011 02:12, Mark H Weaver writes:
> Ludovic, Andy and I discussed this on IRC, and came to the conclusion
> that UTF-8 should be the encoding assumed by functions such as
> scm_c_define, scm_c_define_gsubr, scm_c_define_gsubr_with_generic,
> scm_c_export, scm_c_define_mo
On Fri 18 Mar 2011 11:17, l...@gnu.org (Ludovic Courtès) writes:
> I would add a ‘current-bytecode-endianness’ fluid in (language assembly
> compile-bytecode). The ‘compile’ procedure would have an optional
> ‘endianness’ parameter, which would set this fluid. And ‘guile-tools
> compile’ would h
Hello all,
Now that GNU is in the Google SoC, I'd like to propose again a CPAN for
Guile. (It does needs a proper name, but that name doesn't have to
correspond to the name of the command-line utility; see my other mail
about "guido".)
The proposal would be to start from dorodango, and to use st
Hello all,
Like many of you, I am enamored of the "git style" of command line
interfaces: "git add this", "git commit that", etc.
Guile has guile-tools, which, though not well documented, does support
this. "guile-tools compile foo" loads the `(scripts compile)' module,
and punts argument proces
14 matches
Mail list logo
