PageRenderTime 53ms CodeModel.GetById 23ms RepoModel.GetById 0ms app.codeStats 0ms

/test/subjects/benchmarks/php_bs/xml/rss.xml

http://phc.googlecode.com/
XML | 295 lines | 293 code | 1 blank | 1 comment | 0 complexity | 9d942c0fc4233391727aca31340e4efd MD5 | raw file
Possible License(s): GPL-2.0, 0BSD, BSD-3-Clause, Unlicense, MPL-2.0-no-copyleft-exception, LGPL-2.1
  1. <?xml version="1.0"?>
  2. <!-- RSS generated by UserLand Frontier v9.0 on Fri, 14 Nov 2003 17:43:09 GMT -->
  3. <rss version="2.0" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule">
  4. <channel>
  5. <title>PHP Everywhere</title>
  6. <link>http://php.weblogs.com/</link>
  7. <description>Daily news, articles and free source code on PHP, the popular web scripting language, and other Web technologies.</description>
  8. <creativeCommons:license>http://creativecommons.org/licenses/by-nc/1.0/</creativeCommons:license>
  9. <language>en-us</language>
  10. <pubDate>Mon, 02 Dec 2002 08:00:00 GMT</pubDate>
  11. <lastBuildDate>Tue, 03 Dec 2002 02:06:38 GMT</lastBuildDate>
  12. <docs>http://backend.userland.com/rss</docs>
  13. <generator>UserLand Frontier v9.0</generator>
  14. <category domain="http://www.weblogs.com/rssUpdates/changes.xml">rssUpdates</category>
  15. <managingEditor>jlim@natsoft.com.my (John Lim)</managingEditor>
  16. <webMaster>heyjohnlim@yahoo.com (John Lim)</webMaster>
  17. <item>
  18. <title>NASA Software Engineering Laboratory</title>
  19. <link>http://sel.gsfc.nasa.gov/website/documents/online-doc.htm</link>
  20. <description>A list of software engineering documents derived from over 20 years of software development practice at NASA. Here are the ones i found most useful:
  21. &lt;p&gt;
  22. -Recommended Approach to Software Development &lt;a href=http://sel.gsfc.nasa.gov/website/documents/online-doc/81-305new.pdf&gt;PDF&lt;/a&gt;
  23. &lt;p&gt;
  24. -Manager&apos;s Handbook for Software Development &lt;a href=http://sel.gsfc.nasa.gov/website/documents/online-doc/84-101.pdf&gt;PDF&lt;/a&gt;
  25. &lt;p&gt;
  26. -Software Process Improvement Guide &lt;a href=http://sel.gsfc.nasa.gov/website/documents/online-doc/95-102.pdf&gt;PDF&lt;/a&gt;
  27. &lt;p&gt;
  28. PS: These methods are an insight into how to manage a very big project. For smaller projects, many of these details are bureaucracy and are not needed. I found the requirements and planning parts particularly useful as it has several checklists on things to consider...
  29. &lt;p&gt;
  30. &lt;img src=&quot;http://static.userland.com/shortcuts/images/zeldman/bbll.gif&quot;&gt;</description>
  31. <category>998</category>
  32. <guid>http://php.weblogs.com/2003/11/13#a2114</guid>
  33. </item>
  34. <item>
  35. <title>PEAR2: The interface is the framework</title>
  36. <link>http://php.weblogs.com/2003/11/11#a3125</link>
  37. <description>&lt;i&gt;PEAR1 is now suffering from the fact that it focused from a long period of
  38. building technical foundations without planning the community growth at the
  39. same time.&lt;/i&gt; -- Lukas Smith.
  40. &lt;p&gt;
  41. Now that the cat is out of the bag about PEAR&apos;s problems, I will give my 2 cents worth.
  42. &lt;p&gt;
  43. Firstly, I want to say that I am a PEAR user, but not a PEAR developer. I do use code from PEAR, everyday. There is some first class code in there. But yes I do see problems, and I also have a radical solution at the very end of this essay.
  44. &lt;p&gt;
  45. The biggest problem IMHO with PEAR is the arbitrary way things are apparently run. Why is one class accepted, and another rejected? If it is because they do the same thing, then why are there so many classes that do the same thing in PEAR?
  46. &lt;p&gt;
  47. My perception is that
  48. &lt;ul&gt;
  49. &lt;li&gt;there is no planning except for flavour of the day
  50. &lt;li&gt;there are egos in the community, so people introduce new classes rather than rewrite existing ones to add new functionality
  51. &lt;li&gt; poor design in some of the original classes makes it impractical to extend the original classes
  52. &lt;li&gt; the quality of PEAR is uneven, brilliant gems combined with duds - and the problem is that the duds begin with the &lt;a href=http://news.php.net/article.php?group=php.pear.dev&amp;article=23410&gt;base classes (PEAR and PEAR_Error)&lt;/a&gt;
  53. &lt;li&gt;
  54. &lt;/ul&gt;
  55. &lt;p&gt;
  56. How can things improve? Obviously PEAR2 must be designed to grow with the community. One way to grow in an open source world (if there is no leader with the stature of Linus in the community) is to give everyone a chance to contribute their own code fairly, without the arbitrariness that we see today.
  57. &lt;p&gt;
  58. &lt;img src=http://images.google.com/images?q=tbn:4e6IwJZPGKoC:www.dnaco.net/~ivanjs/images/police.gif align=right&gt;In the Perl world, we have CPAN, where there is no thought police telling you that your code is not acceptable - you just register as a developer, declare a namespace, and upload. Yes there is lots of code duplication, and yes there is no coding standard - but i do perceive that it is fair.
  59. &lt;p&gt;
  60. I have a suggestion for PEAR. I think they need to be more open, and allow multiple people to develop similar classes for the same category. What the PEAR group could do is standardize the API&apos;s for specific categories. This API defines a minimum inter-operatable subset of code for a specific category. Poor documentation will be less of an issue if all contributed code share a common base API.
  61. &lt;p&gt;
  62. I can see some similar classes in PEAR share common APIs informally, but it would be better if it were standardized, so it is less arbitrary and more inclusive. In fact, PHP5 has a good way of enforcing this contract with the &lt;i&gt;implements &lt;/i&gt;keyword. The launch of PHP5 is also a good time to start, because we can finally put PEAR exceptions to sleep and use built-in exceptions.
  63. &lt;p&gt;&lt;p&gt;
  64. Now here comes the &lt;b&gt;really radical suggestion&lt;/b&gt; - if your contributed class conforms to that category&apos;s unit tests, it should be accepted into PEAR. No ifs, no buts, no thought police. And how would you pick which class to use if there are 10 implementations? Let the PHP community decide! Votes or download statistics could be displayed to &quot;fairly&quot; quantify the best code contribution for a category.
  65. &lt;p&gt;&lt;p&gt;
  66. Lastly, I want to remind everyone that standardizing on a common API does not inhibit creativity, provided that the API is sensibly chosen. For example, ADOdb and MDB both have a PEAR DB emulation layer. In fact common APIs do encourage innovation within a shared framework (eg. the BSD forks go in different directions but share code).
  67. &lt;p&gt;&lt;p&gt;Thanks for listening.
  68. &lt;p&gt;
  69. &lt;img src=&quot;http://static.userland.com/shortcuts/images/zeldman/caryg.gif&quot;&gt;</description>
  70. <category>997-2003</category>
  71. <guid>http://php.weblogs.com/2003/11/11#a3125</guid>
  72. </item>
  73. <item>
  74. <title>Today I ran JBoss for the first time</title>
  75. <link>http://php.weblogs.com/2003/11/11#a3128</link>
  76. <description>Another personal milestone i just wanted to note before i forget.</description>
  77. <category>997-2003</category>
  78. <guid>http://php.weblogs.com/2003/11/11#a3128</guid>
  79. </item>
  80. <item>
  81. <title>Smash the Windows</title>
  82. <link>http://www.guardian.co.uk/comment/story/0,3604,1078616,00.html</link>
  83. <description>As our society becomes ever more dependent on information technology, the gulf between those who understand computers and those who don&apos;t will get wider and wider. In 50 years, perhaps much less, the ability to read and write code will be as essential for professionals of every stripe as the ability to read and write a human language is today. If your children&apos;s children can&apos;t speak the language of the machines, they will have to get a manual job - if there are any left -- Dylan Evans.
  84. &lt;p&gt;
  85. &lt;img src=&quot;http://static.userland.com/shortcuts/images/zeldman/bebe.gif&quot;&gt;</description>
  86. <category>997-2003</category>
  87. <guid>http://php.weblogs.com/2003/11/11#a3117</guid>
  88. </item>
  89. <item>
  90. <title>A Turning point for PEAR?</title>
  91. <link>http://php.weblogs.com/2003/11/10#a3118</link>
  92. <description>A posting in the php.pear.dev newsgroup by one of PEAR&apos;s leading developers. I think this is a very honest assessment, and I&apos;m hopeful about this.
  93. &lt;pre&gt;
  94. &gt; From: Xavier Noguer [mailto:xnoguer#xavier-noguer.com]
  95. &gt; Sent: Saturday, November 08, 2003 3:41 PM
  96. &gt; Martin Jansen &amp;lt;mj#php.net&gt; escribi&amp;oacute;
  97. &gt;
  98. &gt; &gt; (http://pear.php.net/manual/en/developers.contributing.php)
  99. &gt; &gt;
  100. &gt; &gt; It is pretty funny to see how much developers have actually read the
  101. &gt; &gt; &quot;Developers Guide&quot; ...
  102. &gt;
  103. &gt; I&apos;ve read that guide. I just don&apos;t seem to be able to take it seriously
  104. &gt; when
  105. &gt; it lists requirements that have never, as far as I know, been voted by the
  106. &gt; pear group or the developer community at large, such as regressions tests
  107. &gt; (http://cvs.php.net/diff.php/peardoc/en/guide/developers/contributing.xml?
  108. &gt; r1=1.8&amp;r2=1.9&amp;ty=h)
  109. &lt;p&gt;I agree here.
  110. While previous mistakes don&apos;t make a wrong a right, I think our whole manual
  111. lacks any consistent concept of what we really feel needs to happen when and
  112. where.
  113. &lt;p&gt;Anyways we have a bunch of messes that are a result of the long period of
  114. limited peer review, followed by a period of package inflation, followed by
  115. the today ruling confusion.
  116. &lt;p&gt;I think its time we fix our standards by starting from a clean slate with a
  117. PEAR2. There we can think about how to best deal with our developer and
  118. users base and how to great the best possible code in a PHP version which
  119. actually supports our needs for OOP.
  120. &lt;p&gt;PEAR1 should of course be maintained as we all have an interest to keep that
  121. code running and to use PEAR1 as a momentum towards a PEAR2 which build on
  122. the past experience.
  123. &lt;p&gt;&amp;lt;rant&gt;
  124. PEAR1 is now suffering from the fact that it focused from a long period of
  125. building technical foundations without planning the community growth at the
  126. same time. This has lead to numerous problems and is making us very
  127. inefficient. Of course PEAR1 has a lot to offer, but I don&apos;t think we are
  128. scaling well and past mistakes seem to haunt us more and more, which we
  129. don&apos;t seem to be able to fix. So I think we need to recognize our past which
  130. we of course need to maintain to remain credible, but at the same time we
  131. should work to build a more scalable PEAR2 in which we can address our
  132. issues on a clean slate.
  133. &amp;lt;/rant&gt;
  134. &lt;p&gt;&gt; Would you be so kind to point me to the pear group document or public
  135. &gt; discussion in which this requirement was approved?
  136. &lt;p&gt;There is no such decision I can remember.
  137. As George pointed out we discussed this point in Amsterdam, however I don&apos;t
  138. remember that anyone decided on requiring documentation at first commit.
  139. However our decisions there were mostly only concepts and not complete.
  140. Anyways maybe someone should check when this was commited anyways.
  141. &lt;p&gt;Regards,
  142. Lukas Smith
  143. &lt;/pre&gt;
  144. &lt;p&gt;
  145. &lt;img src=&quot;http://static.userland.com/shortcuts/images/zeldman/bluey.gif&quot;&gt;</description>
  146. <category>997-2003</category>
  147. <guid>http://php.weblogs.com/2003/11/10#a3118</guid>
  148. </item>
  149. <item>
  150. <title>Is Novell-SuSE deal a brilliant Big Blue power play?</title>
  151. <link>http://techupdate.zdnet.com/techupdate/stories/main/novell_suse.html</link>
  152. <description>Perhaps the most interesting take on the Novell-SuSE deal is the above link. What has been missed by other commentators is that this is a tri-partite agreement with IBM. David Berlind clarifies a lot of things, even if it is still not the full picture.
  153. &lt;p&gt;
  154. Red Hat is also not standing still, abandoning its hobbyist roots to sell only to Enterprises. As &lt;a href=http://infoworld.com/article/03/11/06/HNredhatfedora_1.html&gt;Bruce Perens says&lt;/a&gt;, &quot;&lt;i&gt;The open source community is supposed to produce Fedora so Red Hat can put a stamp on it and charge lots of money for it&lt;/i&gt;.&quot;
  155. &lt;p&gt;
  156. Does anyone have any recommendations for free Linux distros? Ease of installation and use are more important to me than power (hey, the first computer i ever bought was a Mac.)
  157. &lt;p&gt;
  158. PS: Bj&amp;ouml;rn Schotte has some &lt;a href=http://www.phpconference.de/2003/photos_en.php&gt;groovy pictures&lt;/a&gt; of the recent PHP Conference 2003 in Germany.
  159. &lt;p&gt;
  160. &lt;img src=&quot;http://static.userland.com/shortcuts/images/zeldman/dukem.gif&quot;&gt;</description>
  161. <category>997-2003</category>
  162. <guid>http://php.weblogs.com/2003/11/07#a3107</guid>
  163. </item>
  164. <item>
  165. <title>ADOdb 4.02 released with PHP5 suppport</title>
  166. <link>http://php.weblogs.com/adodb#downloads</link>
  167. <description>Been playing around with PHP5. ADOdb 4.02 now works transparently with both PHP4 and PHP5. If PHP5 is detected then the following features will be automatically enabled:
  168. &lt;p&gt;&lt;b&gt;Support for PHP5 iterator overloading&lt;/b&gt;
  169. &lt;p&gt;&lt;pre&gt;
  170. $rs = $DB-&gt;Execute(&quot;select * from table&quot;);&lt;br&gt;
  171. foreach($rs as $row =&gt; $fields) &amp;#123; var_dump($fields); &amp;#125;
  172. &lt;/pre&gt;
  173. &lt;p&gt;&lt;b&gt;Support for PHP5 exceptions&lt;/b&gt;
  174. &lt;p&gt;Just include adodb-exceptions.inc.php and you can now catch exceptions on connection and execute errors as they occur.
  175. &lt;p&gt;&lt;pre&gt;
  176. include(&quot;../adodb-exceptions.inc.php&quot;);
  177. include(&quot;../adodb.inc.php&quot;);
  178. try &amp;#123;
  179. $db = NewADOConnection(&quot;oci8&quot;);
  180. $db-&gt;Connect(&apos;&apos;,&apos;scott&apos;,&apos;bad-password&apos;);
  181. &amp;#125; catch (exception $e) &amp;#123;
  182. var_dump($e);
  183. &amp;#125;
  184. &lt;/pre&gt;
  185. &lt;p&gt;&lt;p&gt;
  186. I managed to surprise myself, the PHP5 iterator code is backward compatible with PHP4, even though the IMPLEMENTS keyword is illegal in PHP4, thanks to the magic of includes.
  187. &lt;p&gt;
  188. And IMHO, the PHP5 iterator implementation with &lt;i&gt;IteratorAggregate &lt;/i&gt;and &lt;i&gt;Iterator&lt;/i&gt;, though powerful, is too complicated - certainly not in the spirit of PHP.
  189. &lt;p&gt;
  190. &lt;img src=&quot;http://static.userland.com/shortcuts/images/zeldman/57.gif&quot;&gt;</description>
  191. <category>997-2003</category>
  192. <guid>http://php.weblogs.com/2003/11/05#a3100</guid>
  193. </item>
  194. <item>
  195. <title>PHP 4.3.4</title>
  196. <link>http://www.php.net/release_4_3_4.php</link>
  197. <description>&lt;i&gt;After a lengthy QA process, PHP 4.3.4 is finally out!
  198. This is a medium size maintenance release, with a fair number of bug fixes. All users are encouraged to upgrade to 4.3.4.
  199. &lt;p&gt;
  200. &lt;b&gt;Bugfix release&lt;/b&gt; &lt;br&gt;
  201. PHP 4.3.4 contains, among others, following important fixes, additions and improvements:
  202. &lt;p&gt;
  203. Fixed disk_total_space() and disk_free_space() under FreeBSD. &lt;br&gt;
  204. Fixed FastCGI being unable to bind to a specific IP. &lt;br&gt;
  205. Fixed several bugs in mail() implementation on win32. &lt;br&gt;
  206. Fixed crashes in a number of functions. &lt;br&gt;
  207. Fixed compile failure on MacOSX 10.3 Panther. &lt;br&gt;
  208. Over 60 various bug fixes! &lt;br&gt;&lt;/i&gt;
  209. &lt;p&gt;The bug-fix that most concerns me most is this one:
  210. &lt;p&gt;
  211. &lt;code&gt;Fixed bug 25404 (ext/pgsql: open transactions not closed when script ends).
  212. &lt;/code&gt;
  213. &lt;p&gt;
  214. In our early days with PHP, we used MySQL a lot. Nowadays, most of our PHP work is with PostgreSQL and Oracle (with the occasional MSSQL project). MySQL is still a good database, but without triggers and views, it no longer meets our company&apos;s needs.</description>
  215. <category>997-2003</category>
  216. <guid>http://php.weblogs.com/2003/11/04#a3092</guid>
  217. </item>
  218. <item>
  219. <title>Sun, Zend integrate PHP with Sun&apos;s Web server</title>
  220. <link>http://www.infoworld.com/article/03/11/03/HNsunzend_1.html?source=rss&amp;url=http://www.infoworld.com/article/03/11/03/HNsunzend_1.html</link>
  221. <description>&lt;i&gt;Zend, oversees the development of PHP and also sells a commercial implementation of the technology. On Monday it released two products that integrate with Version 6.1 of Sun&apos;s Java System Web Server, allowing companies to deploy PHP on Sun&apos;s software. (The Java System Web Server was known previously as the Sun ONE Web Server.)
  222. &lt;p&gt;
  223. The two products are the PHP Enabler, which is intended to let PHP programs run smoothly on Sun&apos;s Web server, and the Zend Performance Suite, which uses code acceleration, content caching and other software tricks to improve the performance of PHP on the Sun platform, the companies said. &lt;/i&gt;
  224. &lt;p&gt;
  225. &lt;img src=&quot;http://static.userland.com/shortcuts/images/zeldman/aca.gif&quot;&gt;</description>
  226. <category>997-2003</category>
  227. <guid>http://php.weblogs.com/2003/11/04#a3088</guid>
  228. </item>
  229. <item>
  230. <title>Icky Sticky Leaky PHPloat</title>
  231. <link>http://php.weblogs.com/2003/11/03#a3085</link>
  232. <description>After running PHP5 beta 2 for 2 days on Apache 1.3 (multi-threaded SAPI on Windows), I was surprised to find that the process was taking 500 Mb. There must be lots of memory leaks. I&apos;m pretty happy that most PHP code just runs, but obviously it&apos;s not production ready.
  233. &lt;p&gt;
  234. Now the hard work starts, how to integrate new PHP5 functionality without impacting old PHP4 code. After thinking a while, I realize there are only a few things I can do to write portable code:
  235. &lt;ul&gt;
  236. &lt;li&gt;In PHP5, we use __clone() to duplicate objects. To make this portable, simply check the PHP_VERSION:
  237. &lt;pre&gt;
  238. $obj2 = (PHP_VERSION &gt;= 5) ? $this-&gt;__clone() : $this;
  239. &lt;/pre&gt;
  240. &lt;li&gt;Error-handling can be encapsulated in a separate function, and conditionally included based on PHP version. Eg.
  241. &lt;pre&gt;
  242. if (PHP_VERSION &gt;= 5) include(&quot;exceptions.inc.php&quot;);
  243. else include(&quot;error.inc.php&quot;);
  244. &lt;/pre&gt;
  245. &lt;p&gt;&lt;/ul&gt;&lt;p&gt;Unfortunately, most other features require explicit use of keywords that are illegal in PHP4, eg. private, protected, implements, etc. These require maintaining a separate codebase for both versions of PHP, or some special pre-processing to be done on the code depending on the versions.
  246. Does anyone have a better suggestion?
  247. &lt;p&gt;
  248. PS: I will be releasing a new version of ADOdb soon, one that should be compatible with PHP5.
  249. &lt;p&gt;
  250. &lt;img src=&quot;http://static.userland.com/shortcuts/images/zeldman/damned2.gif&quot;&gt;</description>
  251. <category>997-2003</category>
  252. <guid>http://php.weblogs.com/2003/11/03#a3085</guid>
  253. </item>
  254. <item>
  255. <title>PHP 5 beta 2 is out</title>
  256. <link>http://php.net/</link>
  257. <description>Just downloaded the Windows install and tested it.
  258. &lt;p&gt;
  259. To run on Apache, I copied php4apache.dll to the php5 root directory, and modified Apache&apos;s httpd.conf:
  260. &lt;pre&gt;
  261. LoadModule php5_module c:/php5/php5b2/php4apache.dll
  262. AddModule mod_php5.c
  263. AddType application/x-httpd-php .php
  264. &lt;/pre&gt;
  265. &lt;p&gt;
  266. For some reason, php_mysql.dll is not working. The error message is &quot;The procedure entry point mysql_create_db could not be located in the dynamic link library LIBMYSQL.dll&quot;. I made sure that the LIBMYSQL.dll was the one that came with the PHP release. I&apos;m using MySQL 4.0.12. Perhaps someone can comment on this.
  267. &lt;p&gt;
  268. However Oracle&apos;s oci8 extension is working fine. As most of our software runs on Oracle, it was easy for us to continue testing PHP5. 99% of all code ran fine. The only gotcha i found was that if your function returns a reference, you can no longer do this:
  269. &lt;p&gt;
  270. &lt;pre&gt; return $this-&gt;function();&lt;/pre&gt;
  271. &lt;p&gt;
  272. but have to change your code to this:
  273. &lt;p&gt;
  274. &lt;pre&gt; $ret =&amp; $this-&gt;function(); # &amp; is not needed if you don&apos;t support PHP4
  275. return $ret;
  276. &lt;/pre&gt;
  277. &lt;p&gt;
  278. A very impressive beta release except for the above glitches.
  279. &lt;p&gt;
  280. &lt;img src=&quot;http://static.userland.com/shortcuts/images/zeldman/nubet.gif&quot;&gt;</description>
  281. <category>997-2003</category>
  282. <guid>http://php.weblogs.com/2003/10/31#a3081</guid>
  283. </item>
  284. <item>
  285. <title>A different take on PHP-Con</title>
  286. <link>http://blogs.gotdotnet.com/bgold/PermaLink.aspx/8176f336-8b28-40f1-82ee-ff00e0c5c1d0</link>
  287. <description>&lt;i&gt;Before I came down I was worried about how I would be accepted by this crowd as a Microsoft representative. Would it be hostile? Would it be open? &lt;/i&gt;
  288. &lt;p&gt;
  289. &lt;img src=&quot;http://static.userland.com/shortcuts/images/zeldman/jackd.gif&quot;&gt;</description>
  290. <category>997-2003</category>
  291. <guid>http://php.weblogs.com/2003/10/30#a3078</guid>
  292. </item>
  293. </channel>
  294. </rss>