Just now on IRC I got a question on has_index() and multisets. It turns out (in various pike versions) that
Pike v7.4 release 11 running Hilfe v3.5 (Incremental Pike Frontend)
mixed m= (<"foo","bar">); m["foo"];
(1) Result: 1
has_index(m,"foo");
(2) Result: 0
search(indices(m),"foo");
(3) Result: 1
wich is not consistent with the documentation, right?
It's a bug in has_index (or rather the internal index_no_free, which I don't know exactly when it's used). I've fixed it now. Thanks.
/ Martin Stjernholm, Roxen IS
Previous text:
2003-08-05 13:17: Subject: has_index()
Just now on IRC I got a question on has_index() and multisets. It turns out (in various pike versions) that
Pike v7.4 release 11 running Hilfe v3.5 (Incremental Pike Frontend)
mixed m= (<"foo","bar">); m["foo"];
(1) Result: 1
has_index(m,"foo");
(2) Result: 0
search(indices(m),"foo");
(3) Result: 1
wich is not consistent with the documentation, right?
/ Peter Lundqvist (disjunkt)
I can understand that. Well, as long as it isn't a problem with roxen/caudium I guess it is pretty much non critical.
/ Peter Lundqvist (disjunkt)
Previous text:
2003-08-05 16:38: Subject: has_index()
It's fixed in 7.4. I'm a bit wary about changing 7.2.
/ Martin Stjernholm, Roxen IS
pike-devel@lists.lysator.liu.se
-
Martin Stjernholm, Roxen IS ＠ Pike developers forum -
Peter Lundqvist (disjunkt) ＠ Pike (-) developers forum