I do not know if that idea is still valid. However, here are two more
to add to that list:
- Integration with Emacs. Guile has a very-nearly-complete
implementation of Elisp. We'd like to get it to the point that it can
actually run Emacs, and see if we can implement GNU's editor better
than the s
Mark H Weaver writes:
> However, catch/throw _will_ accept uninterned symbols created with
> 'make-symbol'.
Personally, I like uninterned symbols much better. They can be a bit
confusing in Lisp because they share print names, but one can't exactly
say that they do in Guile:
guile> (make-symbo
David Kastrup writes:
> Mark H Weaver writes:
>
>> David Kastrup writes:
>>
>>> The symbol name is not garbage collected. That is the difference
>>> between gensym and make-symbol.
>>
>> Integers are plentiful and cheap.
>
> We are not talking about an integer generated statically here. We ar
Mark H Weaver writes:
> David Kastrup writes:
>
>> Andy Wingo writes:
>>
>>> On Sun 04 Mar 2012 13:01, David Kastrup writes:
>>>
The global symbol space is a different identity space than heap
equality, and it never gets garbage collected: the lifetime of a
gensym is eternal.
>>
David Kastrup writes:
> Andy Wingo writes:
>
>> On Sun 04 Mar 2012 13:01, David Kastrup writes:
>>
>>> The global symbol space is a different identity space than heap
>>> equality, and it never gets garbage collected: the lifetime of a
>>> gensym is eternal.
>>
>> This is not true in Guile, whe
On Sun 04 Mar 2012 16:03, Mark H Weaver writes:
Pretty nasty, but we should continue this conversation in the other
thread.
>>>
>>> What other thread?
>>
>> The one about gensym names and peval.
>
> I don't know of any recent thread about gensym names and peval. Do you
> mean the threa
Hello,
On Sun 04 Mar 2012 14:59, David Kastrup writes:
> Andy Wingo writes:
>
>> This is not true in Guile, where symbols can be garbage collected.
>
> The symbol name is not garbage collected. That is the difference
> between gensym and make-symbol.
Not sure I catch your meaning here...
>>
Hi!
I am going trough the list of the ideas for the Google Summer of Code
2011.
I am wondering if this list is still valid:
http://www.gnu.org/software/soc-projects/ideas-2012.html#guile
Otherwise, do you have something to suggest?
Thanks!
Giuseppe
Andy Wingo writes:
> On Sun 04 Mar 2012 00:59, Mark H Weaver writes:
>
+(define compute-base-name
>>>
>>> Pretty nasty, but we should continue this conversation in the other
>>> thread.
>>
>> What other thread?
>
> The one about gensym names and peval.
I don't know of any recent thread
Andy Wingo writes:
> Hi David,
>
> On Sun 04 Mar 2012 13:01, David Kastrup writes:
>
>> The global symbol space is a different identity space than heap
>> equality, and it never gets garbage collected: the lifetime of a
>> gensym is eternal.
>
> This is not true in Guile, where symbols can be ga
Hi David,
On Sun 04 Mar 2012 13:01, David Kastrup writes:
> The global symbol space is a different identity space than heap
> equality, and it never gets garbage collected: the lifetime of a
> gensym is eternal.
This is not true in Guile, where symbols can be garbage collected.
> I am not dism
Andy Wingo writes:
> On Fri 02 Mar 2012 02:35, David Kastrup writes:
>
>> Sure, but things like gensym and make-prompt-tag (and (list '()) for
>> creating an eq?-unique object) are artificial hygiene coming at a cost
>> in symbol table and symbol generation time rather than "lexical"
>> hygiene.
Hi,
An answer to your one question:
On Sun 04 Mar 2012 00:59, Mark H Weaver writes:
>>> +(define compute-base-name
>>
>> Pretty nasty, but we should continue this conversation in the other
>> thread.
>
> What other thread?
The one about gensym names and peval.
Happy hacking,
Andy
--
htt
On Sat 03 Mar 2012 22:20, l...@gnu.org (Ludovic Courtès) writes:
> I’d prefer a solution where libguile-internal threads and locks are
> suitably handled upon fork (basically what wip-threads-and-fork does),
> and where users are provided with mechanisms to do the same at their
> level–which boils
14 matches
Mail list logo
