Re: RFC: Syntax::Construct

[BrowserUk]

This will be taken to be harsh. It is not intended to be so.

This smacks of holiday boredomitis.

In me it manifests itself in the form of expending gratuitous amounts of time attempting to perfect 'good enough' solutions.

In you, it appears to take the form of proposing publishable, but pointless, solutions to invented problems.

Anyone encountering a use Syntax::Construct qw[ ... ]; statement will expend far more time looking up that module and working out what it is 'doing for them'; than they would need to expend if it didn't exist.

Anyone relatively new to Perl (< 4 years) will just assume that the facilities are available through the familiar mechanisms.

Anyone one with longer experience will already be familiar with use 5.010; and use feature qw[ ... ];.

The upshot is that your module would create confusion/waste-the-time-of people in both camps and benefit almost noone.

(You alone might benefit.)

[Jenda]

OK, let me see. I'm writing some code, I need to use some feature that I've heard is not available in some old versions. What do I do ... I basically have three options. First, I can investigate, find out what version introduced that thing and use The.Right.Version. How likely is that I do that? Second, I know my version does support that feature so I add use My.Version.Of.Perl. This means that for no good reason I've disallowed people running older Perls than mine using my script/module. This happens all too often! Third, I specify, in the code, that I want to use that feature. And do not have to know when was the feature introduced.

OK, the other side ... I want to use a module/script. Well ... I might be careful and read the code first, but most likely I'll just run it. In case of a module, I'll run the tests. If the author did the first thing, then either it runs or it tells me my perl is too old. If he did the second ... again it either runs or reports my perl is too old. The catch is I've got no chance knowing which of the two it was and whether the script/module really needs version X.Y or whether M.N would suffice, but the script/module author did not bother checking. In a perfect world use 5.14; means the script/module will not function properly in a lower version. In the real world it more often means the author had 5.14 and that's what he tested the code with.

If the author decided to do the third (actually for him even easier than just use His.Version), I get a compile time message telling me that the script/module uses feature X that was introduced in version X.Y. Pointless, huh?

So ... the only case in which this adds complexity is when someone reads the code, instead of attempting to run or compile-time-check it. And what a huge complexity that is! I see the line, I run "perldoc Syntax::Construct", get told that "this module ensures the specified feature is available in your perl and enables it's use. It reports the necessary perl version in case your perl doesn't support that feature. To test whether your perl supports the requested feture run perl -MSyntax::Construct=... -e 1 in your shell/command prompt."

Huge complexity indeed.

Update: s/\bpdoc\b/perldoc/g; # forgot, pdoc is just a local alias

<!-- Node text goes above. Div tags should contain sig only -- >

[Anonymous Monk]

... investigate ...

perlver does the investigation

... Jenda ...

:)

[BrowserUk]

C:\test>pdoc
'pdoc' is not recognized as an internal or external command,
operable program or batch file.

Okay. Two people.