Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use diagnostics #145

Open
stdweird opened this issue Mar 8, 2017 · 3 comments
Open

use diagnostics #145

stdweird opened this issue Mar 8, 2017 · 3 comments

Comments

@stdweird
Copy link
Member

stdweird commented Mar 8, 2017

See http://perldoc.perl.org/diagnostics.html

Proposal to switch it on on Test::Quattor::Object (so enabled for all unittests), and also add it to the standard PM module template (so enabled for all perl modules that use it).

It's trivial to implement

@stdweird stdweird added this to the 17.3 milestone Mar 8, 2017
@jouvin
Copy link
Contributor

jouvin commented Mar 21, 2017

See Stackoverflow: http://stackoverflow.com/questions/6397170/is-there-any-problem-with-use-diagnostics. Not necessarily for production use...

@jrha
Copy link
Member

jrha commented Mar 21, 2017

Might be a good idea during unittests only.

@ned21
Copy link
Contributor

ned21 commented Mar 21, 2017

Also this comment suggests we can pipe the warnings from a logfile to the splain programme to get the same info?

@jrha jrha modified the milestones: 17.6, 17.3 Mar 27, 2017
@jrha jrha removed this from the 17.8 milestone Sep 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants