I would say yes they are, just like perltie

Where as perltie problem is performance, the lock_keys problem is promotion, just what is it for?

I find this post very telling Re: Should we consider locked hashes a failed experiment? - nntp.perl.org

If this discussion somehow leads to a faster perltie for xs modules, that would be good :)

Maybe this sheds some light 

#!/usr/bin/perl --

use strict;
use warnings;


use Benchmark 'cmpthese';
use Hash::Util();
use Tie::Hash::FixedKeys ();

our %fudge= ( 1,1,3,3 );
our %judge = ( 1,1,3,3 );
our %budge = ( 1,1,3,3 );
our %mudge = ( 1,1,3,3 ); 

Hash::Util::lock_keys(%fudge);
tie %budge, 'Tie::Hash::FixedKeys', keys %budge;
cmpthese( -3, {
    'lock'   => '$fudge{1}++; eval{$fudge{r}++};  ',
    'die'    => '$judge{1}++; eval{$judge{r}++;die};  ',
    'fix'    => '$budge{1}++; eval{$budge{r}++;};  ',
    'fatal'  => '$mudge{{1,1}->{1}}++; eval{use warnings FATAL => qw(u
+ninitialized); $mudge{{1,1}->{r}}++;};    ',
    'olock'   => '$fudge{1}++; ',
    'odie'    => '$judge{1}++; ',
    'ofix'    => '$budge{1}++; ',
    'ofatal'  => '$mudge{{1,1}->{1}}++; ',
});
__END__

[download]
            Rate    fix  fatal   ofix   lock    die ofatal  olock   odie
fix       5127/s     --   -96%   -96%   -97%   -98%   -99%  -100%  -100%
fatal   114761/s  2138%     --    -5%   -31%   -46%   -76%   -97%   -97%
ofix    120289/s  2246%     5%     --   -28%   -43%   -75%   -97%   -97%
lock    167169/s  3161%    46%    39%     --   -21%   -65%   -96%   -96%
die     212804/s  4051%    85%    77%    27%     --   -55%   -94%   -95%
ofatal  477397/s  9211%   316%   297%   186%   124%     --   -88%   -90%
olock  3861974/s 75226%  3265%  3111%  2210%  1715%   709%     --   -15%
odie   4569982/s 89036%  3882%  3699%  2634%  2048%   857%    18%     --

In reply to Re: Are Restricted/Locked Hashes a Failed Experiment? (yes, like perltie, benchmark) by Anonymous Monk
in thread Are Restricted/Locked Hashes a Failed Experiment? by Corion

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.