in reply to altering value in tied hash

each says:

> Tied hashes may have a different ordering behaviour to perl's hash implementation.

The documentation of BerkeleyDB doesn't mention anything, so if you really want to know, you should study the source, probably these six thousand lines of XS.

($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,

[download]

Replies are listed 'Best First'.
Re^2: altering value in tied hash
by Anonymous Monk on Jun 26, 2016 at 09:25 UTC

    The documentation of BerkeleyDB doesn't mention anything, so if you really want to know, you should study the source, probably these six thousand lines of XS.

    :) thats funny choroba but no

    First thing to try is to clean up the code so each tie/untie is in its own scope, and try that

[reply]
      perl 5.10.0
$BerkeleyDB::db_version 4.6

      [download]

      When I put the four operations (load tied hash, assess hash, modify hash, reassess hash) in separate files and run them sequentially, I get the same results.

[reply]
[d/l]

        :D You're missing a version number

        Anyway, its a bug, report it to the author, pmqs@cpan.org

        It may be a bug in "db" itself resolved in a new version

        It may be expected behaviour (unlikely) which ought to be documented

        The author/developer/maintainer ought to have an idea

[reply]

In Section Seekers of Perl Wisdom