[DGD] Minor issue

[Raymond Jennings]

Also, just so you know

DGD itself does not support TLS, only access via call_trace() to writable
arrays that the kernel library just happens to have set up properly so that
it can create the TLS api itself.

On Fri, Feb 3, 2017 at 4:28 PM, Raymond Jennings <shentino at gmail.com> wrote:

> At what exact abstraction/api level are you trying to access the TLS api?
>
> The baseline version is stored on the call stack, but the version
> presented by the klib itself is different
>
>
>
>
> On Fri, Feb 3, 2017 at 3:08 PM, Blain <blain20 at gmail.com> wrote:
>
>> I'm having a minor issue with passing extra args to a newly-cloned object
>> if another object is cloned during the process.  I'm using LWO's for
>> object
>> tracking, and the call to new_object() is overwriting TLSVAR(0) which
>> clone_object() set.  I am trying but to modify the kernel too much, but
>> will have to to fix this.  I was wondering if maybe DGD could be changed
>> grab the args from TLS (or Auto could pass them along with
>> ::clone_object()) and then pass them to _F_create().
>>
>> -Blain
>> ____________________________________________
>> https://mail.dworkin.nl/mailman/listinfo/dgd
>
>
>