Re: New Threshold Syntax
Holger Weiß <[email protected]>
| Newsgroups | gmane.network.nagios.plugins.devel |
|---|---|
| Organization | Freie Universität Berlin |
| Message-ID | <[email protected]> |
* Páll Guðjón Sigurðsson <[email protected]> [2013-09-03 11:43]: > I would personally like to see the new threshold syntax move forward > once someone is willing to spend the proper resources on it. In the > meantime you guys can help out a lot and give this alternative syntax a > better name than "the new threshold syntax". We claim to support it in > pynag, but 10 years from now my code will look really silly if it > references "the new threshold syntax" everywhere. I see you point, but *I* am incredibly bad at naming things, so someone else will have to jump in. > On those notes, we try to follow very closely the guidelines that you > guys give us, namely plugin developer guidelines and extra-opts > guidelines, no matter what we think of them Hehe, I don't know why, but for some reason I get the feeling your're not completely brimmed over with enthusiasm for these terrific standards! > but one thing that would help us a lot if you can put a version number > (or even just a date) on the guidelines that you post. Good point, will do. Holger ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________________ Nagios Plugin Development Mailing List Nagiosplug-devel-5NWGOfrQmneRv+LV9MX5upmplPMkL2fr@public.gmane.orget Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel ::: Please include plugins version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null