[wp-trac] Re: [WordPress Trac] #4779: Proposal for HTTP POST and REQUEST API

[WordPress Trac]

#4779: Proposal for HTTP POST and REQUEST API
--------------------------------------------------+-------------------------
 Reporter:  darkdragon                            |        Owner:  anonymous
     Type:  enhancement                           |       Status:  new      
 Priority:  normal                                |    Milestone:  2.6      
Component:  Optimization                          |      Version:           
 Severity:  normal                                |   Resolution:           
 Keywords:  has-patch needs-testing dev-feedback  |  
--------------------------------------------------+-------------------------
Comment (by DD32):

 > One more thing, pluggable functions are wrapped using the colon...endif;
 blocks.

 Ignoring the current pluggable.php format, Whats the stance on the use of
 endif; in WordPress?[[BR]]
 The coding standards mearly state the preferential use of the Braces, the
 longhand format of if () : endif; is not mentioned, nor is it mentioned in
 the PEAR docs. It makes sense in some places in the code (Some of the
 template functions where a large ammount of code is not fully indented, or
 has many levels) But the longhand method is also used in some places where
 it's really doesnt make sense to use it.(No examples off hand)

 Any core dev carification on that? if () { ... } for short blocks, if ():
 endif; for longer blocks?

 I'm fine for whatever, But i wont bother updateing the patch unless a dev
 actually indicates that its likely to be commited(Or a bug/feature gets
 added to current patch :))

-- 
Ticket URL: <http://trac.wordpress.org/ticket/4779#comment:18>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software