[gambit-list] (##resolve-referencing-objects obj) => list of the objects that reference obj implementation, feedback welcome.

Mikael mikael.rcv at gmail.com
Tue Jun 18 21:36:15 EDT 2013


2013/6/19 Mikael <mikael.rcv at gmail.com>

>
>
> 2013/6/19 Mikael <mikael.rcv at gmail.com>
>
>
>>
>> Space for improvement or things to note are:
>>
>>
> [..]
>

 * If when not in a ##resolve-referencing-objects call there'd be any
referenced to ___SCMOBJ :s on the heap that are == -1 , there'd be a
corresponding number of add_resolved_referencing_object calls made per GC
without any corresponding get_next_resolved_referencing_object  calls, causing
a serious memory leak.

   Probably we better have a global boolean variable
"scanning_for_references" that ##resolve-referencing-objects switches the
scanning mode on/off, as to secure against unintended
add_resolved_referencing_object calls?

 * There's no handling of malloc() failure on add_resolved_referencing_
object , leading to a potential sigsegv. Gambit's other malloc() call does
the same though.


>
>
>> Feedback?
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.iro.umontreal.ca/pipermail/gambit-list/attachments/20130619/74f07012/attachment.htm>


More information about the Gambit-list mailing list