Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

Re^2: Code tags warning

by Roy Johnson (Monsignor)
on Mar 14, 2005 at 18:18 UTC ( #439393=note: print w/replies, xml ) Need Help??


in reply to Re: Code tags warning
in thread Code tags warning

Frankly, yes. People quickly learn to ignore things that are always there. But when something different pops up, they tend to take notice. It's a little like the difference between what perl does under use warnings, versus how helpful it would be if perl simply told you not to use uninitialized variables every time it ran.

Caution: Contents may have been coded under pressure.

Replies are listed 'Best First'.
Re^3: Code tags warning
by Whitehawke (Pilgrim) on Mar 14, 2005 at 22:15 UTC

    People quickly learn to ignore things that are always there.

    One way to deal with this would be to select the wording of the message at random (a la 'fortune'). So, you might forget the code tags on four separate occasions and get a different one of the following each time:

        Code tags in your posts, 
        These are a great goodness, true
        Alas, all unfound
    
            (or the alternate version of the above:)
      
            Code tags in your posts, 
            These are a great goodness, true
            Unlike this haiku
    
    
        Code tags, code tags, wherefore art thou code tags?
    
    
        You know...that looks a lot like a code snippet, 
        but nary a code tag in sight.  You sure you want 
        to post?
    
    
        I'm sorry <username>, I'm afraid I can't do that.
        At least, not until you add some code tags.
    
      I like it just for the amusement factor. But I think the fact that no message appears except when the system determines they've got untagged code, the warnings won't suffer from "always there" syndrome.

      Sadly, even if we were to randomize the hint text, it would quickly take on a background noise quality. Because it's still always there in some form, whereas the warnings would only come up when there's a reason to grab the user's attention.


      Caution: Contents may have been coded under pressure.
      I'm all for encouraging proper posting, but let's remember that newbies are the most likely to commit a posting faux pas are exactly the ones who need help the most.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://439393]
help
Chatterbox?
[marioroy]: The MCE::Hobo::Pool module will come later.
[Corion]: marioroy: Oh, that's always cool, having API-compatible modules. This makes testing and comparing things much easier
[marioroy]: IPC in MCE::Shared can handle 400k (sends) per second. That's seems a lot for being a pure-Perl module. After making the release, will come back and post a solution for a node by a fellow wanting faster logging.
[Corion]: While working on WWW::Mechanize:: Chrome, I had the suspicion that AnyEvent was doing something wrong, but I was able to swap it out for Mojolicious and the error persisted.
[Corion]: Of course, the error was in my own code ;)
[marioroy]: Corion, start and start_child in MCE::Hobo::Manager return a MCE::Hobo object, whereas P::FM returns the PID. I can have it return the PID though. I tried Hobo::Manager with several P::FM modules, just changed P::FM to MCE::Hobo::Manager and it works.

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (6)
As of 2017-05-26 08:36 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?