Sanko Robinson

Sigh. Reverting and documenting. Here's what went wrong: The prototype for `Readonly::Readonly(...)` is made to accept just about everything (simple scalars, hashref, etc.) so it doesn't care about undefined (not...

@pghmcfc that seems to be something else entirely. Works fine over the old `tie()` API (if I change the test to use `Readonly::Scalar1 ...`) but not the XS/built-in version (uses...

@pghmcfc Found it. Weird that a smoker with Readonly::XS installed didn't shake this one out long ago. Should be resolved in 1.60.

Responding on my phone via email so this might not be well formatted. The function Readonly() creates shallow read only vars. What I think you want is a deep read...

Yeah the documentation is even more misleading than the ironically named `Readonly()` function. What you expect to happen here is what the `Readonly::Scalar()`, `::Hash()`, and `::Array()` functions do. Plain `Readonly()`...

This is going to get wordy... I have no idea why he started expanding the API with poorly named functions that do the same thing `Readonly()` does. I agree with...

I wasn't ignoring this, just... not 100% sure what to do with blessed objects besides document that they aren't handled by Readonly. I really like the idea of being able...

> I am aware that non-strictness is a source of bugs, but in this particular case it needs sloppy, sloppy, sloppy developers to run into that bug. And that sloppy...

> When you get to that final line, the code croaks, but when you contruct the object, you can pass in anything you want. @Ovid, your reply was made first...

Neat bit of code. I'm sure someone out there would appreciate it being on CPAN. I've been planning to raise this here for a few months and already understood that...