Re^2: Was a module use'd or require'd?

in reply to Re: Was a module use'd or require'd?
in thread Was a module use'd or require'd?

This is merely for a debugging module to offer hints for what's going on under the hood. That's all. It's for developers only, not intended for code to rely on and it has heavy caveats about what the output is and why it is intended as a crutch, but should not be relied upon.

Cheers,
Ovid

New address of my CGI Course.

Comment on Re^2: Was a module use'd or require'd?

Replies are listed 'Best First'.
Re^3: Was a module use'd or require'd? by BrowserUk (Patriarch) on Aug 13, 2007 at 19:55 UTC
This is merely for a debugging module to offer hints for what's going on under the hood. I understand that, but I still can't see the purpose. That is, to derive any benefit from a hint that a module was required rather than used, when debugging or otherwise, there would have to be some practical, effective difference in the way the module performed in those two scenarios. If there is no difference, then there is no benefit to knowing. And if there is a difference, then eventually someone is going to find a way of either: exploiting that difference to provide some additional functionality. detecting that difference so as to counter the effects of it in the way their module performs. Since I couldn't (and still cannot) think of any difference in the way a module would perform dependant upon whether it was required or used, I couldn't see the benefit of jumping through hoops to make the determination. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]

Replies are listed 'Best First'.

Re^3: Was a module use'd or require'd?
by BrowserUk (Patriarch) on Aug 13, 2007 at 19:55 UTC

This is merely for a debugging module to offer hints for what's going on under the hood.

I understand that, but I still can't see the purpose. That is, to derive any benefit from a hint that a module was required rather than used, when debugging or otherwise, there would have to be some practical, effective difference in the way the module performed in those two scenarios. If there is no difference, then there is no benefit to knowing.

And if there is a difference, then eventually someone is going to find a way of either:

exploiting that difference to provide some additional functionality.
detecting that difference so as to counter the effects of it in the way their module performs.

Since I couldn't (and still cannot) think of any difference in the way a module would perform dependant upon whether it was required or used, I couldn't see the benefit of jumping through hoops to make the determination.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

[reply]

In Section Seekers of Perl Wisdom