08-09-2017
Programming guidelines and style
Hello all,
I would like to know if there is a generally accepted unix shell programming Guideline?
Do you have any idea where to find this?
There are a lot of programming Guidelines to find over Google, but is there one who is generally accepted?
4 More Discussions You Might Find Interesting
1. Forum Support Area for Unregistered Users & Account Problems
This area is not for technical questions. It is reserved for unregistered users who have a question or registered users who have trouble with their account.
Other posts will be deleted by the moderators. (0 Replies)
Discussion started by: Neo
0 Replies
2. What is on Your Mind?
This area is not for forum specific technical questions. Please post forum specific technical questions in the best forum, not in the lounge. However, if your idea or question is not covered clearly in a forum, please post it here.
Discuss whatever is on your mind. Technical topics welcome... (0 Replies)
Discussion started by: Neo
0 Replies
3. Shell Programming and Scripting
Hi,
I was wondering if any of you guys have developed shell scripting guidelines for writing unix shell scripts effectively. This includes naming standards, comments, indentation, error handing after unix comands, use of exported variables, sending notifications, functions, logging etc...
... (2 Replies)
Discussion started by: acheepi
2 Replies
4. Programming
Hello to all,
Here is my situation. Some time in the mid-80's I stumbled across a small white programming book - can't remember the name but it was unique in that it started right out giving instructions on creating building blocks in code as a foundation for a complete system. The book was... (2 Replies)
Discussion started by: jozefn
2 Replies
LEARN ABOUT DEBIAN
net::google::code::issue::search
Net::Google::Code::Issue::Search(3pm) User Contributed Perl Documentation Net::Google::Code::Issue::Search(3pm)
NAME
Net::Google::Code::Issue::Search - Issues Search API
DESCRIPTION
INTERFACE
search ( can => 'all', q = 'foo', sort => '-modified', limit => 1000, load_after_search => 1 )
do the search, the results is set to $self->results,
which is an arrayref with Net::Google::Code::Issue as element.
If a "sort" argument is specified, that will be passed to google code's issue list. Generally, these are composed of "+" or "-"
followed by a column name.
limit => Num is to limit the results number.
load_after_search => Bool is to state if we should call $issue->load after search
return true if search is successful, false on the other hand.
updated_after( date_string || DateTime object )
find all the issues that have been updated or created after the date. the issues are all loaded.
return true if success, false on the other hand
project
results
this should be called after a successful search. returns issues as a arrayref.
AUTHOR
sunnavy "<sunnavy@bestpractical.com>"
LICENCE AND COPYRIGHT
Copyright 2008-2010 Best Practical Solutions.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.10.1 2010-01-29 Net::Google::Code::Issue::Search(3pm)