Unix::setuid is a poorly worked out idea. Firstly because it doesn't report errors in any way (despite typically being used in security-critical ways). Secondly because it omits the saved IDs (which are fairly important). That said, I do like the...

What I hate most about the system is that it doesn't offer me a way to get back into contact with the rater. Maybe they are mistaken about something essential, maybe I fixed a legitimate issue they reported. Maybe I'd...

This is a terrible idea really: any change to your bundle mean breaking backwards compatibility. This sort of breakage-at-a-distance can be hard to diagnose. To some extend you can deal with it using a versioning argument (like Modern::Perl does nowadays),...

Quite frankly anyone asking for a scanned copy of an identification document is an idiot: you can not verify the authenticity using a copy. Even a crappy forge is likely to be accepted. Sending it by non-encrypted email doesn't make...

Why the dependency on Moose and v5.10? The latter seems rather unnecessary, and the former poorly chosen (lots of dependencies, while using few of it's features: Moo sounds like it would be much more appropriate)....

I think there are two kind of sponsored people. The first category are the Damians of our community. These are people whose attendance at any conference provides an immediate and obvious benefit every time you'd invite them. People like me...

Have you taken a look at [TOML](https://github.com/toml-lang/toml)? IMO it provides a much more sensible paradigm than INI, while still being intuitive enough for most people. There are already two parser for it in Perl....

More often than not you can hack on a module without Dist::Zilla just fine. Tests can usually be run simply as `prove -lr t/`, so usually you can actually hack on the code and test the results without touching dzil....

> It looks interesting; it seems to solve several of C++'s more egregious problems (e.g. garbage collection). Actually, I consider garbage collection to be the main mistake in D. In such a low level language, I don't want garbage collection....

> I've always wondered why CPAN does not at least show a full dependency list (what will be pulled in, not necessarily the full dependency list) similar to the way that yum does prior to launching into what can turn...

CGI still lives for the same reasons as inetd still lives: services that are queried only infrequently (with a "frequently" being defined by the sysadmin), keeping a process in memory is wasteful. Exactly. CGI is the only sensible thing...

people expect to build, test and install in separate phases It's not just that people expect it, it's that sysadmin will demand it. Friendliness to the end-user is just as important as friendliness to the author, if not more...

There's a flaw IMHO, read() may not return the whole file content (and actually it won't with large files), depends on OS buffering. The usual boilerplate includes a while() and buffer concatenation. Actually, you're right. Normally the buffering takes...

Leon has started his own Module::Build::Tiny and while admirable (and impressive) it cannot do XS yet. Until this is possible or until Moodule::Build or some other candidate emerges, EUMM and MB are the only way to go. Actually, I...

Because File::Slurp is portable to non-Unix systems. Functionally it's identical to read_file(binmode => ':raw'), otherwise it's perfectly portable. Because File::Slurp can be rewritten in XS if speed is the overriding concern (and it will be faster than your 2-lines)....

If I recall, File::Slurp had issues with the PerlIO :encoding layer and required manual decoding of the slurped data instead, which is why I have avoided it. Not sure if this is still an issue. Looking at the code,...

Comment Threads

Maybe create some phase gates for new contributors? or create some kind of bar to get over before you can upload and even get rated in the first place?

prepan.org exists as a place where authors can upload code for critique, but it doesn't get used often enough. I wouldn't mind the requirement for a new author to make at least one submission to prepan.org first (and get some positive feedback) before their first PAUSE upload, but this is difficult to enforce without a lot of code that no one would want to write.

If you want this, first make the guys writing books about perl not tell new developers to submit their code to CPAN; I've read 2 such books. I am sure there are more books out there saying the same thing.

I am also unclear on your reasoning for the problem. Is it: 1) because you don't like how long the module list is with the extra entries? 2) The submissions of Acme:: and related modules are …

Also, note that in the case of "actual data determining your data structure" IOD is not different from YAML which trinita uses: whether a parameter is scalar or array is still determined by the config. Config::MVP is different in that it uses some sort of "outside schema" to specify that a parameter needs to have a certain form/value.

Come to think of it, Unix::setuid is not necessary at all, because I might as well just localize $, et al directly! The only convenience provided by Unix::setuid is conversion from username, but I'm not sure how valuable that is.

About blogs.perl.org

blogs.perl.org is a common blogging platform for the Perl community.
Written in Perl and offering the modern features you’ve come to
expect in blog platforms, the site is run by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.