bulk88:

UseMI64

• I don't care for the name, but I can't think of anything better, either.
• For the return value, I'd *always* return the 'before call' value, though. The reason being that if you want to query & change, you currently need two calls. But it's also for the principle of least surprise: I generally write (and see) "setter" type functions that return either the original object (so you can chain calls) or the prior value (so you can restore it after some operation).
• I think I'd default the setting to 'on' if you're using a perl that doesn't support quads. (I contemplated suggesting using the 'Q' arg type there too, but it doesn't "feel" clean to me that way.)

SafeReadWideCString

I don't care for returning an empty string to signify the conversion error. I think I'd return undef or die on all errors so the user can catch it in an eval block. The empty string is too close to being legitimate, as the user might've passed an empty string *in*. If you want to split your errors into groups, I'd suggest returning undef for one group, and die for the other.

Having said all that, keep in mind that these are my opinions, and they're worth exactly what you paid for 'em. ;^)

...roboticus

When your only tool is a hammer, all problems look like your thumb.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.