Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

Re: [wp-hackers] Inline documentation

  • To: wp-hackers@xxxxxxxxxxxxxxxxxxxx
  • Subject: Re: [wp-hackers] Inline documentation
  • From: Roy Schestowitz <r@xxxxxxxxxxxxxxx>
  • Date: Wed, 15 Feb 2006 19:19:53 +0000
  • Delivery-date: Wed, 15 Feb 2006 19:19:58 +0000
  • Envelope-to: s@schestowitz.com
  • In-reply-to: <43F373EB.7000505@atl.lmco.com>
  • References: <43F33C8D.2010509@rcbowen.com> <80f75db0602150853o510486b3p4ea2aaa2558a1c90@mail.gmail.com> <5aa3aa0602150901y1317ec46n5e0e23e22bac9013@mail.gmail.com> <43F373EB.7000505@atl.lmco.com>
  • User-agent: Internet Messaging Program (IMP) H3 (4.0.3)
_____/ On Wed 15 Feb 2006 18:33:15 GMT, [Doug Stewart] wrote : \_____

Craig wrote:
As someone who wants to learn PHP via dissecting WordPress, I'd love to see
this. I think it would be worth the extra cost of file weight. Besides,
"bloat" is really about functionality that is better attached via plugin or
other means, and should never be used in conjunction with adding value to
code by making it easier to understand and therefore use, change, or

Hey, I've got an idea - ship two .zips, a .dev edition with full comments and a .standard edition with no whitespace whatsoever.

Sorry. I'll go back to lurking.

Comment ought to be accumulated and always remain in tact in the repository. Each time release milestone is reached, run a parser which strips all comments and publish.

Developers can fetch documented code of interest from the SVN repository,
the nightly, or a Developer Edition. It is worth using the same tactic with
debugging bits in the code. If there are none, something in development
model is probably missed.


[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index