I'm trying to fully understand the history as presented by git. One of
the things I can't work out is this:
Take a look at src/pike_memory.c on the 7.8 branch in gitk. For the
last few commits it says 7.7 and 7.8 branches only, which is what I
expect. But at the commit Added DMALLOC_USE_HASHBASE
could you please post the commit ids?
greetings, martin.
Added DMALLOC_USE_HASHBASE mode is
fe982070cac0283b79a3a4a3a54b7865537acab7.
Also regarding src/pike_memory.c, its history starts with
memory.{c,h} renamed to pike_memory.{c,h}
(4e86f944a018c5397e3c55693b0637f63987e7d7). Regardless of -M, -C and
--find-copies-harder flags, I can't see the history
On Sat, Sep 06, 2008 at 12:40:02PM +, Martin Stjernholm, Roxen IS @ Pike
developers forum wrote:
Added DMALLOC_USE_HASHBASE mode is
fe982070cac0283b79a3a4a3a54b7865537acab7.
ah, i think i see the problem.
it looks like the backports somehow get indicated as whole merges.
not sure what
Martin Baehr wrote:
On Sat, Sep 06, 2008 at 12:40:02PM +, Martin Stjernholm, Roxen IS @ Pike
developers forum wrote:
Added DMALLOC_USE_HASHBASE mode is
fe982070cac0283b79a3a4a3a54b7865537acab7.
ah, i think i see the problem.
it looks like the backports somehow get indicated as whole
If I have a reference to another object, and I'd like to make that
reference a weak reference (from within a CMOD, or from Pike), what is
the best way to change it?
set_weak_flag() appears not to operate on object references.
--
Sincerely,
Stephen R. van den Berg.
You cannot propel
set_weak_flag operates on a reference container, not the reference
itself.
