[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Pika-dev] so... string work
From: |
Matthew Dempsky |
Subject: |
Re: [Pika-dev] so... string work |
Date: |
Sat, 24 Jan 2004 17:01:30 +0100 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) |
Tom Lord <address@hidden> writes:
> So, to sum up the implications for Pika of that long thing:
>
> Strings will be "vtable objects" containing a pointer to a `t_udstr'
> (see src/hackerlab/strigns).
I meant to ask this earlier, but when you say the vtable object should
contain "a pointer to a t_udstr", is that intentional or accidental?
Since t_udstr itself is a pointer value and I don't see any hackerlab
routines yet that require a t_udstr *, am I missing something?
A routine like:
t_udstr scm_string_value (t_scm_arena arena, t_scm_word * value);
should have a GC-independant lifetime like the scm_big(num|rat)_value
functions.
-jivera
- [Pika-dev] so... string work, Tom Lord, 2004/01/22
- [Pika-dev] Re: so... string work, Jose A. Ortega Ruiz, 2004/01/23
- Re: [Pika-dev] so... string work,
Matthew Dempsky <=
- Re: [Pika-dev] so... string work, Tom Lord, 2004/01/24
- Re: [Pika-dev] so... string work, Tom Lord, 2004/01/24
- Re: [Pika-dev] so... string work, Matthew Dempsky, 2004/01/24
- Re: [Pika-dev] so... string work, Tom Lord, 2004/01/24
- Re: [Pika-dev] so... string work, Matthew Dempsky, 2004/01/24
- Re: [Pika-dev] so... string work, Tom Lord, 2004/01/24
- Re: [Pika-dev] so... string work, Matthew Dempsky, 2004/01/25
- Re: [Pika-dev] so... string work, Tom Lord, 2004/01/25
- Re: [Pika-dev] so... string work, Matthew Dempsky, 2004/01/25
- Re: [Pika-dev] so... string work, Tom Lord, 2004/01/25