BEGIN:VCALENDAR
VERSION:2.0
X-WR-CALNAME:19/12/2006: On The Legibility of PHP
X-WR-CALDESC:David Segall wrote:  I do not deny that the programmer is the most significant factor in the readability of a program but would you really promote PHP as a language because it is easy to read?  I certainly wouldn&#8217;t advise against it because of legibility concerns.  Any language that supports comments (not all do) and allows the programmer to choose variable and function identifiers using arbitrary alphanumeric names (again, not all do) can be made very readable simply by using these facilities. With most common programming languages, you can easily clarify your code by having a policy that includes choosing sensible, readable function and variable names, using indentation and plenty of white space, adding liberal comments, keeping line lengths down to a reasonable length, keeping function sizes down to 20 or so lines (longer functions can often be split into two or more functions). Yes, even Perl!    For example, consider the following two (untested) PHP objects which are exactly&#8230;
BEGIN:VJOURNAL
DTSTART:20070903T022715Z
DTEND:20070903T022715Z
URL:http://tobyinkster.co.ukhttp://tobyinkster.co.uk/blog/2006/12/19/php-legibility/comments#comment1
SUMMARY:Comment 001
CATEGORIES:
STATUS:NEEDS-ACTION
END:VJOURNAL
BEGIN:VJOURNAL
DTSTART:20071108T222414Z
DTEND:20071108T222414Z
URL:http://tobyinkster.co.ukhttp://tobyinkster.co.uk/blog/2006/12/19/php-legibility/comments#comment2
SUMMARY:Comment 002
CATEGORIES:
STATUS:NEEDS-ACTION
END:VJOURNAL
BEGIN:VJOURNAL
DTSTART:20080207T184637Z
DTEND:20080207T184637Z
URL:http://tobyinkster.co.ukhttp://tobyinkster.co.uk/blog/2006/12/19/php-legibility/comments#comment3
SUMMARY:Comment 003
CATEGORIES:
STATUS:NEEDS-ACTION
END:VJOURNAL
BEGIN:VJOURNAL
DTSTART:20080217T233142Z
DTEND:20080217T233142Z
URL:http://tobyinkster.co.ukhttp://tobyinkster.co.uk/blog/2006/12/19/php-legibility/comments#comment4
SUMMARY:Comment 004
CATEGORIES:
STATUS:NEEDS-ACTION
END:VJOURNAL
BEGIN:VJOURNAL
DTSTART:20080218T001208Z
DTEND:20080218T001208Z
URL:http://tobyinkster.co.ukhttp://tobyinkster.co.uk/blog/2006/12/19/php-legibility/comments#comment5
SUMMARY:Comment 005
CATEGORIES:
STATUS:NEEDS-ACTION
END:VJOURNAL
BEGIN:VJOURNAL
DTSTART:20080220T134622Z
DTEND:20080220T134622Z
URL:http://tobyinkster.co.ukhttp://tobyinkster.co.uk/blog/2006/12/19/php-legibility/comments#comment6
SUMMARY:Comment 006
CATEGORIES:
STATUS:NEEDS-ACTION
END:VJOURNAL
BEGIN:VJOURNAL
DTSTART:20080225T202556Z
DTEND:20080225T202556Z
URL:http://tobyinkster.co.ukhttp://tobyinkster.co.uk/blog/2006/12/19/php-legibility/comments#comment7
SUMMARY:Comment 007
CATEGORIES:
STATUS:NEEDS-ACTION
END:VJOURNAL
BEGIN:VJOURNAL
DTSTART:20080225T203552Z
DTEND:20080225T203552Z
URL:http://tobyinkster.co.ukhttp://tobyinkster.co.uk/blog/2006/12/19/php-legibility/comments#comment8
SUMMARY:Comment 008
CATEGORIES:
STATUS:NEEDS-ACTION
END:VJOURNAL
BEGIN:VJOURNAL
DTSTART:20080227T212248Z
DTEND:20080227T212248Z
URL:http://tobyinkster.co.ukhttp://tobyinkster.co.uk/blog/2006/12/19/php-legibility/comments#comment9
SUMMARY:Comment 009
CATEGORIES:
STATUS:NEEDS-ACTION
END:VJOURNAL
BEGIN:VJOURNAL
DTSTART:20080308T210729Z
DTEND:20080308T210729Z
URL:http://tobyinkster.co.ukhttp://tobyinkster.co.uk/blog/2006/12/19/php-legibility/comments#comment10
SUMMARY:Comment 010
CATEGORIES:
STATUS:NEEDS-ACTION
END:VJOURNAL
END:VCALENDAR
