Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

Re: Considering duplicates

by footpad (Monsignor)
on Jun 24, 2001 at 20:39 UTC ( #91075=note: print w/replies, xml ) Need Help??


in reply to Considering duplicates

Great reminder...one I'm take advantage of by adding a few things that've been bugging me lately:

When a post is a true duplicate (original author submitted twice without substantial rewrite/rework), it would really help if people would see if either post has replies. If so, then consider the one that doesn't have substantial replies.

And, while we're on the subject, please enter reasons when you consider nodes. Almost every time a node has been considered "silently," I've had to vote Keep--because my personal copy of PSI::ESP seems to have a bad install, if you know what I mean.

Finally, I do not believe the following reasons are valid reasons to consider nodes:

  • "vague"
  • "answered previously"
  • "again?"
  • "poor composition skills"
  • "off-topic"

While these may not be the best nodes on the site, they generally are posted by new members or people who haven't yet learned the ropes. Please consider these opportunities to welcome and educate, rather than to criticize and rebuff. If we want people to feel welcome, then you need to roll out the mat and start smiling when they show up. Please treat them as guests, and not "freaking [l]users."

--f

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://91075]
help
Chatterbox?
[Corion]: haukex: Aaah - I thought you were still running these tests on every machine, but you only run these as author or Devel::Cover tests
[Corion]: haukex: Yeah, I think back then I used Test::Inline, which used a pod parser that was going through some changes and I didn't want to cater for all the various versions and thus stopped testing the Pod completely
[choroba]: I usually do this with presentations
[Corion]: But now I think statically (re)generating the Pod tests is a saner approach, and likely I'll regenerate the tests either in Makefile.PL or from xt/ but have them live below t/
[choroba]: I keep the snippets in files of their own, and use a Makefile to syntax highlight them and insert them into slides, while also running them and inserting the output if required
[Corion]: choroba: Ooooh - I didn't think of that! I write my presentations as POD and if it "roughly" looks like Perl code, I should also syntax-check that...
[haukex]: Yes sorry I don't run them all the time, my POD tests are only run as author tests (and are excluded when I'm using Devel::Cover)
[Corion]: choroba: Hmm - no, I keep the snippets inline, but as my framework also has support for capturing output etc., maybe I should do the same...
[Corion]: haukex: Yes, that approach is sane, and it heals the fragility of Pod parsers in a nice way while still syntax-checking stuff
[choroba]: Unfortunately, none of it is online

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (6)
As of 2017-02-27 12:25 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Before electricity was invented, what was the Electric Eel called?






    Results (385 votes). Check out past polls.