Duh! How a bout another Perl developer using the enverioment that I'm developing?! Well, I say that because I work building softwares for developers, not for end users.

It is very un-perlish to lock something. You don't know what creative solutions others invent using your code, and I think it's better to free your code and let others use your code much the way you use Perl. Locking a scalar makes no sense. It's probably a sign that you need another "user" interface (API). Maybe you want OO with a protected property. Perhaps you just need a simple function that returns a value. But I seriously doubt you really need a scalar that is readonly.

This is just to avoid the user to undef the internal object. This really won't crash all the enverioment, mas it's script won't work until the end. But the enverioment will be still active to can load future scripts.

Well, but if the user really wan't to reset the SCALAR it always can, it just need to make some XS and load it, than it can do everything!

Graciliano M. P.
"Creativity is the expression of the liberty".