Re: [Vala] GObject allocation / referencing... Why is so slow?




Yes, it's not the same, but it's a similar implementation, using
reference counting (it's not atomic, but if you use an sig_atomic_t ref
variable, instead of the volatile int, you would get atomicity with no
performance loss at all),

Not true I believe. sig_atomic_t ensures atomicity on an entirely
different level.
It has nothing to do with multi-threaded programming.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]