[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Dynamic loading progress
From: |
Aurélien Aptel |
Subject: |
Re: Dynamic loading progress |
Date: |
Sun, 4 Oct 2015 16:22:53 +0200 |
On Sun, Oct 4, 2015 at 4:11 PM, Aurélien Aptel
<address@hidden> wrote:
> We have to be careful with this vtable thing. I don't want to end up
> with C++-level complexity with operator overloading, copy/move
><snip>
> module side. For example, a module could return new "types" using a
> cons ('my-type . ID) where ID is an integer index into a pointer table
> handled by the module author. It's more work for module writers but it
> works and keeps the complexity of the module interface low.
To be clear, I still prefer the opaque pointer type with the vtable
thingy solution. I was just showing alternatives.
Re: Dynamic loading progress, Aurélien Aptel, 2015/10/08
Re: Dynamic loading progress, Tom Tromey, 2015/10/08
Re: Dynamic loading progress, Philipp Stephani, 2015/10/08
- Re: Dynamic loading progress, Daniel Colascione, 2015/10/08
- Re: Dynamic loading progress, Philipp Stephani, 2015/10/08
- Re: Dynamic loading progress, Daniel Colascione, 2015/10/08
- Re: Dynamic loading progress, Philipp Stephani, 2015/10/08
- Re: Dynamic loading progress, Aurélien Aptel, 2015/10/08
- Re: Dynamic loading progress, Eli Zaretskii, 2015/10/08
- Re: Dynamic loading progress, Philipp Stephani, 2015/10/14
- Re: Dynamic loading progress, Eli Zaretskii, 2015/10/15
- Re: Dynamic loading progress, Andreas Schwab, 2015/10/15