<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_06_30_1425208</id>
	<title>PHP 5.3 Released</title>
	<author>timothy</author>
	<datestamp>1246372980000</datestamp>
	<htmltext><a href="http://sudheer.satbinaryvibes.co.in/" rel="nofollow">Sudheer</a> writes <i>"The PHP development team is proud to announce the <a href="http://www.php.net/archive/2009.php#id2009-06-30-1">immediate release of PHP 5.3.0</a>. This release is a major improvement in the 5.X series, which includes a large number of new features and bug fixes. Some of the key new features include: namespaces, late static binding, closures, optional garbage collection for cyclic references, new extensions (like ext/phar, ext/intl and ext/fileinfo), over 140 bug fixes and much more."</i></htmltext>
<tokenext>Sudheer writes " The PHP development team is proud to announce the immediate release of PHP 5.3.0 .
This release is a major improvement in the 5.X series , which includes a large number of new features and bug fixes .
Some of the key new features include : namespaces , late static binding , closures , optional garbage collection for cyclic references , new extensions ( like ext/phar , ext/intl and ext/fileinfo ) , over 140 bug fixes and much more .
"</tokentext>
<sentencetext>Sudheer writes "The PHP development team is proud to announce the immediate release of PHP 5.3.0.
This release is a major improvement in the 5.X series, which includes a large number of new features and bug fixes.
Some of the key new features include: namespaces, late static binding, closures, optional garbage collection for cyclic references, new extensions (like ext/phar, ext/intl and ext/fileinfo), over 140 bug fixes and much more.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28552613</id>
	<title>And now the waiting..</title>
	<author>greywire</author>
	<datestamp>1246457580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>.. begins!  Maybe in another 2 years we'll get this into CentOS/Redhat.</p><p>And by the looks of it, we might see PHP 6 around the same time we return to the moon.</p><p>(and I choose the space program as a comparison to another endeavor that seems to be progressing at a rediculously slow pace)</p></htmltext>
<tokenext>.. begins ! Maybe in another 2 years we 'll get this into CentOS/Redhat.And by the looks of it , we might see PHP 6 around the same time we return to the moon .
( and I choose the space program as a comparison to another endeavor that seems to be progressing at a rediculously slow pace )</tokentext>
<sentencetext>.. begins!  Maybe in another 2 years we'll get this into CentOS/Redhat.And by the looks of it, we might see PHP 6 around the same time we return to the moon.
(and I choose the space program as a comparison to another endeavor that seems to be progressing at a rediculously slow pace)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528467</id>
	<title>PHP - more like PFfffHP</title>
	<author>Anonymous</author>
	<datestamp>1246377300000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Just kidding. I know nothing about your programming language.</p><p>All I know is that if you own a Mac you are either gay or bisexual.</p></htmltext>
<tokenext>Just kidding .
I know nothing about your programming language.All I know is that if you own a Mac you are either gay or bisexual .</tokentext>
<sentencetext>Just kidding.
I know nothing about your programming language.All I know is that if you own a Mac you are either gay or bisexual.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28538611</id>
	<title>But PHP is shit!</title>
	<author>UK Boz</author>
	<datestamp>1246383480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Blah de blah PHP is shit because [insert random piece of php code that a programmer could use if they were a complete fuckwit]
Everyone should use [insert my favorite scripting language] because [insert totally irrelevant feature nobody give a fuck about]</htmltext>
<tokenext>Blah de blah PHP is shit because [ insert random piece of php code that a programmer could use if they were a complete fuckwit ] Everyone should use [ insert my favorite scripting language ] because [ insert totally irrelevant feature nobody give a fuck about ]</tokentext>
<sentencetext>Blah de blah PHP is shit because [insert random piece of php code that a programmer could use if they were a complete fuckwit]
Everyone should use [insert my favorite scripting language] because [insert totally irrelevant feature nobody give a fuck about]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530483</id>
	<title>Re:Nuisances</title>
	<author>Stan Vassilev</author>
	<datestamp>1246383960000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p><div class="quote"><p>There's a huge codebase out there that's using PHP against MySQL, and using PHP's original ereg regex syntax instead of the Perl-wannabe stuff. What are they thinking, when they set out to break this?</p></div><p>Nothing is broken. Ereg is moved to the 'official' extension pack called PECL, which you can use for full backwards compatibility. At the same time the community has been warning not to use the ereg functions for the past at least 3-4 years, if not more, citing worse performance, worse featureset, and the possibility of PCRE replacing it at some point in the future.</p></div>
	</htmltext>
<tokenext>There 's a huge codebase out there that 's using PHP against MySQL , and using PHP 's original ereg regex syntax instead of the Perl-wannabe stuff .
What are they thinking , when they set out to break this ? Nothing is broken .
Ereg is moved to the 'official ' extension pack called PECL , which you can use for full backwards compatibility .
At the same time the community has been warning not to use the ereg functions for the past at least 3-4 years , if not more , citing worse performance , worse featureset , and the possibility of PCRE replacing it at some point in the future .</tokentext>
<sentencetext>There's a huge codebase out there that's using PHP against MySQL, and using PHP's original ereg regex syntax instead of the Perl-wannabe stuff.
What are they thinking, when they set out to break this?Nothing is broken.
Ereg is moved to the 'official' extension pack called PECL, which you can use for full backwards compatibility.
At the same time the community has been warning not to use the ereg functions for the past at least 3-4 years, if not more, citing worse performance, worse featureset, and the possibility of PCRE replacing it at some point in the future.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529203</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528673</id>
	<title>Re:features!</title>
	<author>Anonymous</author>
	<datestamp>1246378020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>i think it is great! it signifies that PHP is now the "goto" language for web development. like how some people have a "goto" shirt for a pub night.</p><p>now excuse me while i throw up.</p><p>
&nbsp;</p></htmltext>
<tokenext>i think it is great !
it signifies that PHP is now the " goto " language for web development .
like how some people have a " goto " shirt for a pub night.now excuse me while i throw up .
 </tokentext>
<sentencetext>i think it is great!
it signifies that PHP is now the "goto" language for web development.
like how some people have a "goto" shirt for a pub night.now excuse me while i throw up.
 </sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528473</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529203</id>
	<title>Nuisances</title>
	<author>wytcld</author>
	<datestamp>1246380120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Let's say you've been using PHP since about a month after Rasmus released it 15 years back, so you've got a whole lot of code that uses the ereg family of regex functions. So they've depricated them, and plan to yank them from PHP 6. Why? Is the overhead so terrible? Or do they really think that it will improve our lives if we have to go back through everything and translate eregs to pregs?</p><p>Then there's the change in MySQL password formats. Sure, if they include the latest MySQL libraries they have a different encryption level. But if PHP is smart enough to warn you about that when your MySQL install is still using the older passwords, then PHP should be smart enough to include both libraries and use whichever one is appropriate to the passwords encountered.</p><p>There's a huge codebase out there that's using PHP against MySQL, and using PHP's original ereg regex syntax instead of the Perl-wannabe stuff. What are they thinking, when they set out to break this? When 5.3 rolls out through the distros a whole lot of MySQL backends will fail on the password thing. And when 6.0 rolls out millions of regexs will suddenly be failing. Needlessly.</p></htmltext>
<tokenext>Let 's say you 've been using PHP since about a month after Rasmus released it 15 years back , so you 've got a whole lot of code that uses the ereg family of regex functions .
So they 've depricated them , and plan to yank them from PHP 6 .
Why ? Is the overhead so terrible ?
Or do they really think that it will improve our lives if we have to go back through everything and translate eregs to pregs ? Then there 's the change in MySQL password formats .
Sure , if they include the latest MySQL libraries they have a different encryption level .
But if PHP is smart enough to warn you about that when your MySQL install is still using the older passwords , then PHP should be smart enough to include both libraries and use whichever one is appropriate to the passwords encountered.There 's a huge codebase out there that 's using PHP against MySQL , and using PHP 's original ereg regex syntax instead of the Perl-wannabe stuff .
What are they thinking , when they set out to break this ?
When 5.3 rolls out through the distros a whole lot of MySQL backends will fail on the password thing .
And when 6.0 rolls out millions of regexs will suddenly be failing .
Needlessly .</tokentext>
<sentencetext>Let's say you've been using PHP since about a month after Rasmus released it 15 years back, so you've got a whole lot of code that uses the ereg family of regex functions.
So they've depricated them, and plan to yank them from PHP 6.
Why? Is the overhead so terrible?
Or do they really think that it will improve our lives if we have to go back through everything and translate eregs to pregs?Then there's the change in MySQL password formats.
Sure, if they include the latest MySQL libraries they have a different encryption level.
But if PHP is smart enough to warn you about that when your MySQL install is still using the older passwords, then PHP should be smart enough to include both libraries and use whichever one is appropriate to the passwords encountered.There's a huge codebase out there that's using PHP against MySQL, and using PHP's original ereg regex syntax instead of the Perl-wannabe stuff.
What are they thinking, when they set out to break this?
When 5.3 rolls out through the distros a whole lot of MySQL backends will fail on the password thing.
And when 6.0 rolls out millions of regexs will suddenly be failing.
Needlessly.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529453</id>
	<title>Re:features!</title>
	<author>Anonymous</author>
	<datestamp>1246380960000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p><b>P</b>erverted <b>H</b>omosexual <b>P</b>enetration</p><p>That's what PHP stands for.</p><p>Professional web developers use genuine Microsoft technologies such as ASP.NET.</p></htmltext>
<tokenext>Perverted Homosexual PenetrationThat 's what PHP stands for.Professional web developers use genuine Microsoft technologies such as ASP.NET .</tokentext>
<sentencetext>Perverted Homosexual PenetrationThat's what PHP stands for.Professional web developers use genuine Microsoft technologies such as ASP.NET.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528473</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529351</id>
	<title>Re:Namespaces...about time!</title>
	<author>truthsearch</author>
	<datestamp>1246380600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You didn't get a "function already exists" type of error when it was redeclared?  Strange.</p></htmltext>
<tokenext>You did n't get a " function already exists " type of error when it was redeclared ?
Strange .</tokentext>
<sentencetext>You didn't get a "function already exists" type of error when it was redeclared?
Strange.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528705</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28536059</id>
	<title>Comparison PHP - Java</title>
	<author>Nicopa</author>
	<datestamp>1246363020000</datestamp>
	<modclass>Troll</modclass>
	<modscore>1</modscore>
	<htmltext><p>Some time ago I *had* to work with PHP. I haven't known it before that. Now I hate it =). At that time I wrote a comparison, out of anger about PHP being so much used. This is the <a href="http://www.reloco.com.ar/prog/phpvsjava.html" title="reloco.com.ar">comparison Java - PHP I have wrote</a> [reloco.com.ar].</p></htmltext>
<tokenext>Some time ago I * had * to work with PHP .
I have n't known it before that .
Now I hate it = ) .
At that time I wrote a comparison , out of anger about PHP being so much used .
This is the comparison Java - PHP I have wrote [ reloco.com.ar ] .</tokentext>
<sentencetext>Some time ago I *had* to work with PHP.
I haven't known it before that.
Now I hate it =).
At that time I wrote a comparison, out of anger about PHP being so much used.
This is the comparison Java - PHP I have wrote [reloco.com.ar].</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530859</id>
	<title>Re:Horray</title>
	<author>Anonymous</author>
	<datestamp>1246384800000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>If you can't tell that the parent post is a joke you're probably a PHP programmer.</p></htmltext>
<tokenext>If you ca n't tell that the parent post is a joke you 're probably a PHP programmer .</tokentext>
<sentencetext>If you can't tell that the parent post is a joke you're probably a PHP programmer.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528643</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528643</id>
	<title>Horray</title>
	<author>Anonymous</author>
	<datestamp>1246377900000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>So does this mean I should upgrade from PHP 3.2? Are there any incompatibilities with my existing code?
<br> <br>
Maybe someone can look over my login script and tell me if this will work in PHP5?
<br> <br>
<tt>
$query\_login="select * FROM user";<br>
$result\_login = mysql\_query($query\_login) or die("Your passwrod is might be bad I think");<br><nobr> <wbr></nobr>//$login\_check = mysql\_num\_rows($result\_login);<br>
while($row=mysql\_fetch\_array($result\_login))<br>
{<br>
$username=$row["username"];<br>
if ($username==$username1)<br>
{<br>
echo "";<br>
echo "window.location.href='login\_error.php?rec=qq';";<br>
echo "";<br>
exit;<br>
}<br>
}<br>
</tt></htmltext>
<tokenext>So does this mean I should upgrade from PHP 3.2 ?
Are there any incompatibilities with my existing code ?
Maybe someone can look over my login script and tell me if this will work in PHP5 ?
$ query \ _login = " select * FROM user " ; $ result \ _login = mysql \ _query ( $ query \ _login ) or die ( " Your passwrod is might be bad I think " ) ; // $ login \ _check = mysql \ _num \ _rows ( $ result \ _login ) ; while ( $ row = mysql \ _fetch \ _array ( $ result \ _login ) ) { $ username = $ row [ " username " ] ; if ( $ username = = $ username1 ) { echo " " ; echo " window.location.href = 'login \ _error.php ? rec = qq ' ; " ; echo " " ; exit ; } }</tokentext>
<sentencetext>So does this mean I should upgrade from PHP 3.2?
Are there any incompatibilities with my existing code?
Maybe someone can look over my login script and tell me if this will work in PHP5?
$query\_login="select * FROM user";
$result\_login = mysql\_query($query\_login) or die("Your passwrod is might be bad I think"); //$login\_check = mysql\_num\_rows($result\_login);
while($row=mysql\_fetch\_array($result\_login))
{
$username=$row["username"];
if ($username==$username1)
{
echo "";
echo "window.location.href='login\_error.php?rec=qq';";
echo "";
exit;
}
}
</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528837</id>
	<title>Re:features!</title>
	<author>Anonymous</author>
	<datestamp>1246378680000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext>Guess the only thing missing now is COMEFROM?</htmltext>
<tokenext>Guess the only thing missing now is COMEFROM ?</tokentext>
<sentencetext>Guess the only thing missing now is COMEFROM?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528473</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28540483</id>
	<title>Re:Nuisances</title>
	<author>Anonymous</author>
	<datestamp>1246450980000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>function mysql\_password($passStr)<br>{<nobr> <wbr></nobr>// from somewhere on php.net, can't remember which page...<nobr> <wbr></nobr>// note that mysql have changed the way passwords work<nobr> <wbr></nobr>// so this function corresponds to MYSQL\_OLDPASSWORD on newer databases.<br>
&nbsp; &nbsp; &nbsp; &nbsp; $nr=0x50305735;<br>
&nbsp; &nbsp; &nbsp; &nbsp; $nr2=0x12345671;<br>
&nbsp; &nbsp; &nbsp; &nbsp; $add=7;<br>
&nbsp; &nbsp; &nbsp; &nbsp; $charArr = preg\_split("//", $passStr);</p><p>
&nbsp; &nbsp; &nbsp; &nbsp; foreach ($charArr as $char)<br>
&nbsp; &nbsp; &nbsp; &nbsp; {<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; if (($char == '') || ($char == ' ') || ($char == '\t')) continue;<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; $charVal = ord($char);<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; $nr ^= ((($nr &amp; 63) + $add) * $charVal) + ($nr  8);<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; $nr2 += ($nr2  8) ^ $nr;<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; $add += $charVal;<br>
&nbsp; &nbsp; &nbsp; &nbsp; }</p><p>
&nbsp; &nbsp; &nbsp; &nbsp; return sprintf("\%08x\%08x", ($nr &amp; 0x7fffffff), ($nr2 &amp; 0x7fffffff));<br>}<nobr> <wbr></nobr>// from http://www.puremango.co.uk/2005/02/online\_tools\_76/</p></htmltext>
<tokenext>function mysql \ _password ( $ passStr ) { // from somewhere on php.net , ca n't remember which page... // note that mysql have changed the way passwords work // so this function corresponds to MYSQL \ _OLDPASSWORD on newer databases .
        $ nr = 0x50305735 ;         $ nr2 = 0x12345671 ;         $ add = 7 ;         $ charArr = preg \ _split ( " // " , $ passStr ) ;         foreach ( $ charArr as $ char )         {                       if ( ( $ char = = ' ' ) | | ( $ char = = ' ' ) | | ( $ char = = ' \ t ' ) ) continue ;                       $ charVal = ord ( $ char ) ;                           $ nr ^ = ( ( ( $ nr &amp; 63 ) + $ add ) * $ charVal ) + ( $ nr 8 ) ;                       $ nr2 + = ( $ nr2 8 ) ^ $ nr ;                           $ add + = $ charVal ;         }         return sprintf ( " \ % 08x \ % 08x " , ( $ nr &amp; 0x7fffffff ) , ( $ nr2 &amp; 0x7fffffff ) ) ; } // from http : //www.puremango.co.uk/2005/02/online \ _tools \ _76/</tokentext>
<sentencetext>function mysql\_password($passStr){ // from somewhere on php.net, can't remember which page... // note that mysql have changed the way passwords work // so this function corresponds to MYSQL\_OLDPASSWORD on newer databases.
        $nr=0x50305735;
        $nr2=0x12345671;
        $add=7;
        $charArr = preg\_split("//", $passStr);
        foreach ($charArr as $char)
        {
                      if (($char == '') || ($char == ' ') || ($char == '\t')) continue;
                      $charVal = ord($char);
                          $nr ^= ((($nr &amp; 63) + $add) * $charVal) + ($nr  8);
                      $nr2 += ($nr2  8) ^ $nr;
                          $add += $charVal;
        }
        return sprintf("\%08x\%08x", ($nr &amp; 0x7fffffff), ($nr2 &amp; 0x7fffffff));} // from http://www.puremango.co.uk/2005/02/online\_tools\_76/</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529203</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528827</id>
	<title>It's true!</title>
	<author>3.5 stripes</author>
	<datestamp>1246378620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Years of php programming have danaged my bain to!</p></htmltext>
<tokenext>Years of php programming have danaged my bain to !</tokentext>
<sentencetext>Years of php programming have danaged my bain to!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528555</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529901</id>
	<title>Re:Horray</title>
	<author>chord.wav</author>
	<datestamp>1246382340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>STAY AWAY FROM THE KEYBOARD RIGHT NOW!! That's it, easy, let go... That's all gonna be alright... (Pst! Somebody call 911..)</p></htmltext>
<tokenext>STAY AWAY FROM THE KEYBOARD RIGHT NOW ! !
That 's it , easy , let go... That 's all gon na be alright... ( Pst ! Somebody call 911.. )</tokentext>
<sentencetext>STAY AWAY FROM THE KEYBOARD RIGHT NOW!!
That's it, easy, let go... That's all gonna be alright... (Pst! Somebody call 911..)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528643</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530055</id>
	<title>Re:Nuisances</title>
	<author>DragonWriter</author>
	<datestamp>1246382820000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><blockquote><div><p>There's a huge codebase out there that's using PHP against MySQL, and using PHP's original ereg regex syntax instead of the Perl-wannabe stuff. What are they thinking, when they set out to break this? When 5.3 rolls out through the distros a whole lot of MySQL backends will fail on the password thing. And when 6.0 rolls out millions of regexs will suddenly be failing.</p></div> </blockquote><p>Uh, no.</p><p>Assuming that people running and maintaining the code are paying any attention, when 6.0 rolls out, those installations that have working code relying on features long-announced for deprecation that are removed in 6.0 will <i>not upgrade to 6.0</i>.</p><p>Major new interpreter versions enable new projects, and old projects can be migrated to them if there is a reason. But they aren't intended to be minor, backward compatible, performance improvement and bug fix releases -- that's why they are called major versions.</p></div>
	</htmltext>
<tokenext>There 's a huge codebase out there that 's using PHP against MySQL , and using PHP 's original ereg regex syntax instead of the Perl-wannabe stuff .
What are they thinking , when they set out to break this ?
When 5.3 rolls out through the distros a whole lot of MySQL backends will fail on the password thing .
And when 6.0 rolls out millions of regexs will suddenly be failing .
Uh , no.Assuming that people running and maintaining the code are paying any attention , when 6.0 rolls out , those installations that have working code relying on features long-announced for deprecation that are removed in 6.0 will not upgrade to 6.0.Major new interpreter versions enable new projects , and old projects can be migrated to them if there is a reason .
But they are n't intended to be minor , backward compatible , performance improvement and bug fix releases -- that 's why they are called major versions .</tokentext>
<sentencetext>There's a huge codebase out there that's using PHP against MySQL, and using PHP's original ereg regex syntax instead of the Perl-wannabe stuff.
What are they thinking, when they set out to break this?
When 5.3 rolls out through the distros a whole lot of MySQL backends will fail on the password thing.
And when 6.0 rolls out millions of regexs will suddenly be failing.
Uh, no.Assuming that people running and maintaining the code are paying any attention, when 6.0 rolls out, those installations that have working code relying on features long-announced for deprecation that are removed in 6.0 will not upgrade to 6.0.Major new interpreter versions enable new projects, and old projects can be migrated to them if there is a reason.
But they aren't intended to be minor, backward compatible, performance improvement and bug fix releases -- that's why they are called major versions.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529203</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529215</id>
	<title>Re:Looking Forward To It</title>
	<author>nedwidek</author>
	<datestamp>1246380180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Hallelujah on the register\_globals. At least magic quotes are now deprecated. Here's looking forward to 6.0 when they are finally removed!! (I've talked to way too many devs who think they are adequate protection against SQL injections)</p></htmltext>
<tokenext>Hallelujah on the register \ _globals .
At least magic quotes are now deprecated .
Here 's looking forward to 6.0 when they are finally removed ! !
( I 've talked to way too many devs who think they are adequate protection against SQL injections )</tokentext>
<sentencetext>Hallelujah on the register\_globals.
At least magic quotes are now deprecated.
Here's looking forward to 6.0 when they are finally removed!!
(I've talked to way too many devs who think they are adequate protection against SQL injections)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528597</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528473</id>
	<title>features!</title>
	<author>Lord Ender</author>
	<datestamp>1246377300000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>PHP now comes with more GOTO!</p></htmltext>
<tokenext>PHP now comes with more GOTO !</tokentext>
<sentencetext>PHP now comes with more GOTO!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531747</id>
	<title>Re:Hooray fileinfo is standard!</title>
	<author>Anonymous</author>
	<datestamp>1246387440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Pfffft!</p><p>Everything changed with the release of Drupal (written in PHP).<br>We are creating several large projects each year based on Drupal/PHP and our solutions easily bests any proprietary solutions I've encountered so far.</p></htmltext>
<tokenext>Pfffft ! Everything changed with the release of Drupal ( written in PHP ) .We are creating several large projects each year based on Drupal/PHP and our solutions easily bests any proprietary solutions I 've encountered so far .</tokentext>
<sentencetext>Pfffft!Everything changed with the release of Drupal (written in PHP).We are creating several large projects each year based on Drupal/PHP and our solutions easily bests any proprietary solutions I've encountered so far.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528427</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531343</id>
	<title>Building object-oriented modular PHP applications</title>
	<author>Anonymous</author>
	<datestamp>1246386180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Separation of concerns is a concept in object-oriented (OO) software design that allows you to build more-modular applications. Modular applications are easier to maintain and add new features to. <a href="http://www.ibm.com/developerworks/opensource/library/os-php-objectorient/index.html?ca=dgr-lnxw01PHP-OOdth-o&amp;S\_TACT=105AGX59&amp;S\_CMP=grlnxw01" title="ibm.com" rel="nofollow">PHP's OO language features</a> [ibm.com] allow you to apply design concepts to build more robust, maintainable applications.</p></htmltext>
<tokenext>Separation of concerns is a concept in object-oriented ( OO ) software design that allows you to build more-modular applications .
Modular applications are easier to maintain and add new features to .
PHP 's OO language features [ ibm.com ] allow you to apply design concepts to build more robust , maintainable applications .</tokentext>
<sentencetext>Separation of concerns is a concept in object-oriented (OO) software design that allows you to build more-modular applications.
Modular applications are easier to maintain and add new features to.
PHP's OO language features [ibm.com] allow you to apply design concepts to build more robust, maintainable applications.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530119</id>
	<title>Re:Horray</title>
	<author>Anonymous</author>
	<datestamp>1246383060000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>You can hope all you want, but that's better than a lot of legacy PHP code I've seen. Did you know that, for PHP programmers, base64 is a password encryption method?</p></htmltext>
<tokenext>You can hope all you want , but that 's better than a lot of legacy PHP code I 've seen .
Did you know that , for PHP programmers , base64 is a password encryption method ?</tokentext>
<sentencetext>You can hope all you want, but that's better than a lot of legacy PHP code I've seen.
Did you know that, for PHP programmers, base64 is a password encryption method?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529135</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28532059</id>
	<title>Re:features!</title>
	<author>K. S. Kyosuke</author>
	<datestamp>1246388580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>GOTO has its uses. I never used it (as I prefer a <b>more structured way to code</b>), but critical mission error handling may take advantage of a more direct way to "jump".</p></div></blockquote><p>

Like tail calls instead of gotos?<nobr> <wbr></nobr>;-)</p></div>
	</htmltext>
<tokenext>GOTO has its uses .
I never used it ( as I prefer a more structured way to code ) , but critical mission error handling may take advantage of a more direct way to " jump " .
Like tail calls instead of gotos ?
; - )</tokentext>
<sentencetext>GOTO has its uses.
I never used it (as I prefer a more structured way to code), but critical mission error handling may take advantage of a more direct way to "jump".
Like tail calls instead of gotos?
;-)
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528751</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28532013</id>
	<title>Re:Horray</title>
	<author>Ant P.</author>
	<datestamp>1246388400000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>Don't get your hopes up... I've seen real code that's worse.</p></htmltext>
<tokenext>Do n't get your hopes up... I 've seen real code that 's worse .</tokentext>
<sentencetext>Don't get your hopes up... I've seen real code that's worse.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529135</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528701</id>
	<title>My best feature...</title>
	<author>bogaboga</author>
	<datestamp>1246378080000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>...is the ability to employ <tt>goto</tt>, though it is not allowed to jump into a loop or switch statement. A fatal error is issued in such cases.</p></htmltext>
<tokenext>...is the ability to employ goto , though it is not allowed to jump into a loop or switch statement .
A fatal error is issued in such cases .</tokentext>
<sentencetext>...is the ability to employ goto, though it is not allowed to jump into a loop or switch statement.
A fatal error is issued in such cases.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529845</id>
	<title>Re:Nuisances</title>
	<author>Anonymous</author>
	<datestamp>1246382160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Change is almost always painful and scary but you'll be happy for it in the end.  Update the code and be glad they don't stay backwards compatable to every iteration of the language.</p><p>It's better to clean up and remove the old stuff and continue improving the language.  They don't have enough resources to bugfix and improve such a lengthy/aging codebase.</p></htmltext>
<tokenext>Change is almost always painful and scary but you 'll be happy for it in the end .
Update the code and be glad they do n't stay backwards compatable to every iteration of the language.It 's better to clean up and remove the old stuff and continue improving the language .
They do n't have enough resources to bugfix and improve such a lengthy/aging codebase .</tokentext>
<sentencetext>Change is almost always painful and scary but you'll be happy for it in the end.
Update the code and be glad they don't stay backwards compatable to every iteration of the language.It's better to clean up and remove the old stuff and continue improving the language.
They don't have enough resources to bugfix and improve such a lengthy/aging codebase.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529203</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529821</id>
	<title>Re:Hooray fileinfo is standard!</title>
	<author>Anonymous</author>
	<datestamp>1246382100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Oh wait, almost any PHP project eventually gets reduced to a song and dance of ugly hacks.</p></div><p>I thought that was for every scripting language out there.</p><p><div class="quote"><p>Now I don't have to do a song and dance of ugly hacks to get what I need from a file on systems without the extention.</p></div><p>Yay, we now have closures and gotos and whatnot to do even more ugly hacking!</p></div>
	</htmltext>
<tokenext>Oh wait , almost any PHP project eventually gets reduced to a song and dance of ugly hacks.I thought that was for every scripting language out there.Now I do n't have to do a song and dance of ugly hacks to get what I need from a file on systems without the extention.Yay , we now have closures and gotos and whatnot to do even more ugly hacking !</tokentext>
<sentencetext>Oh wait, almost any PHP project eventually gets reduced to a song and dance of ugly hacks.I thought that was for every scripting language out there.Now I don't have to do a song and dance of ugly hacks to get what I need from a file on systems without the extention.Yay, we now have closures and gotos and whatnot to do even more ugly hacking!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528427</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531365</id>
	<title>Re:Nuisances</title>
	<author>profplump</author>
	<datestamp>1246386240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>They really think having regex functions that aren't binary safe is a bad idea -- besides the obviously disastrous results when used for input validation it also means that ereg cannot support unicode. Plus it's just extra code that there's little reason to continue patching and porting a decade after it has been superseded by faster, safer functions.</htmltext>
<tokenext>They really think having regex functions that are n't binary safe is a bad idea -- besides the obviously disastrous results when used for input validation it also means that ereg can not support unicode .
Plus it 's just extra code that there 's little reason to continue patching and porting a decade after it has been superseded by faster , safer functions .</tokentext>
<sentencetext>They really think having regex functions that aren't binary safe is a bad idea -- besides the obviously disastrous results when used for input validation it also means that ereg cannot support unicode.
Plus it's just extra code that there's little reason to continue patching and porting a decade after it has been superseded by faster, safer functions.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529203</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28537193</id>
	<title>A serious question</title>
	<author>Anonymous</author>
	<datestamp>1246370460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Can anyone give an example of a good use of lambdas in php? I'd appreciate both 1. A situation where you would *have* to use it ( or the way to do it without lambdas is such an ugly, counter-intuitive hack that no one would do it ), and 2. an example of where you might use lambdas naturally.
<br> <br>I've been trying to figure them out since they were announced for 5.3. I think I understand them, but I don't know whey or where you would want to use them.</htmltext>
<tokenext>Can anyone give an example of a good use of lambdas in php ?
I 'd appreciate both 1 .
A situation where you would * have * to use it ( or the way to do it without lambdas is such an ugly , counter-intuitive hack that no one would do it ) , and 2. an example of where you might use lambdas naturally .
I 've been trying to figure them out since they were announced for 5.3 .
I think I understand them , but I do n't know whey or where you would want to use them .</tokentext>
<sentencetext>Can anyone give an example of a good use of lambdas in php?
I'd appreciate both 1.
A situation where you would *have* to use it ( or the way to do it without lambdas is such an ugly, counter-intuitive hack that no one would do it ), and 2. an example of where you might use lambdas naturally.
I've been trying to figure them out since they were announced for 5.3.
I think I understand them, but I don't know whey or where you would want to use them.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528471</id>
	<title>Missing Feature.</title>
	<author>Zarjazz</author>
	<datestamp>1246377300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You forgot the most important change of all.</p><p>They added support for "goto".</p></htmltext>
<tokenext>You forgot the most important change of all.They added support for " goto " .</tokentext>
<sentencetext>You forgot the most important change of all.They added support for "goto".</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528485</id>
	<title>namespaces</title>
	<author>underqualified</author>
	<datestamp>1246377360000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext>about time. way to go guys.<nobr> <wbr></nobr>:D</htmltext>
<tokenext>about time .
way to go guys .
: D</tokentext>
<sentencetext>about time.
way to go guys.
:D</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28532885</id>
	<title>Re:Building object-oriented modular PHP applicatio</title>
	<author>WillKemp</author>
	<datestamp>1246391520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Looks like that link's slashdotted! IBM? Surely not?!</p></htmltext>
<tokenext>Looks like that link 's slashdotted !
IBM ? Surely not ?
!</tokentext>
<sentencetext>Looks like that link's slashdotted!
IBM? Surely not?
!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531343</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28533769</id>
	<title>The main issue with PHP is highlighted here.</title>
	<author>a\_karbon\_devel\_005</author>
	<datestamp>1246395420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The PHP development team has no vision, and they haven't ever had one. It's a hodgepodge that started out to be a "web perl" way back in the day, but then Java developers started using it and so 5 looked more and more Java-esque, but obviously being Java isn't their vision either.

Take the namespacing in this release. They are using the BACKSPACE as the namespace separator. It's f'ing awful and inconsistent, but they wanted to jam it into 5.3<nobr> <wbr></nobr>... even though Dimitri had a patch that would have used "::" for the separator, the PHP devs didn't want to use it because it would have to go in PHP 6.

That's because, just like the inconsistent library arguments, the PHP developer community, like it's user base, is "practical"<nobr> <wbr></nobr>.. they will sacrifice correctness for easiness. It's the same reason there's no way to flip a php.ini directive and have annoying warnings/errors turned into exceptions instead... "It's hard (because our codebase is shitty.)"

PHP sucks, but it doesn't matter to most. It's too popular. But it does suck because there's no consistent vision for it.</htmltext>
<tokenext>The PHP development team has no vision , and they have n't ever had one .
It 's a hodgepodge that started out to be a " web perl " way back in the day , but then Java developers started using it and so 5 looked more and more Java-esque , but obviously being Java is n't their vision either .
Take the namespacing in this release .
They are using the BACKSPACE as the namespace separator .
It 's f'ing awful and inconsistent , but they wanted to jam it into 5.3 ... even though Dimitri had a patch that would have used " : : " for the separator , the PHP devs did n't want to use it because it would have to go in PHP 6 .
That 's because , just like the inconsistent library arguments , the PHP developer community , like it 's user base , is " practical " .. they will sacrifice correctness for easiness .
It 's the same reason there 's no way to flip a php.ini directive and have annoying warnings/errors turned into exceptions instead... " It 's hard ( because our codebase is shitty .
) " PHP sucks , but it does n't matter to most .
It 's too popular .
But it does suck because there 's no consistent vision for it .</tokentext>
<sentencetext>The PHP development team has no vision, and they haven't ever had one.
It's a hodgepodge that started out to be a "web perl" way back in the day, but then Java developers started using it and so 5 looked more and more Java-esque, but obviously being Java isn't their vision either.
Take the namespacing in this release.
They are using the BACKSPACE as the namespace separator.
It's f'ing awful and inconsistent, but they wanted to jam it into 5.3 ... even though Dimitri had a patch that would have used "::" for the separator, the PHP devs didn't want to use it because it would have to go in PHP 6.
That's because, just like the inconsistent library arguments, the PHP developer community, like it's user base, is "practical" .. they will sacrifice correctness for easiness.
It's the same reason there's no way to flip a php.ini directive and have annoying warnings/errors turned into exceptions instead... "It's hard (because our codebase is shitty.
)"

PHP sucks, but it doesn't matter to most.
It's too popular.
But it does suck because there's no consistent vision for it.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528597</id>
	<title>Looking Forward To It</title>
	<author>Anonymous</author>
	<datestamp>1246377780000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>Say what you will about PHP, but it puts food on my table and a good roof over my head.  I have been clamoring for the new features in PHP 5.3.0 (closures, namespaces, they finally killed register\_globals) and can't wait for the improvements coming in 6.<br> <br>I truly appreciate the hard work of the PHP development team and the free language they have given us, congratulations on the new release.</htmltext>
<tokenext>Say what you will about PHP , but it puts food on my table and a good roof over my head .
I have been clamoring for the new features in PHP 5.3.0 ( closures , namespaces , they finally killed register \ _globals ) and ca n't wait for the improvements coming in 6 .
I truly appreciate the hard work of the PHP development team and the free language they have given us , congratulations on the new release .</tokentext>
<sentencetext>Say what you will about PHP, but it puts food on my table and a good roof over my head.
I have been clamoring for the new features in PHP 5.3.0 (closures, namespaces, they finally killed register\_globals) and can't wait for the improvements coming in 6.
I truly appreciate the hard work of the PHP development team and the free language they have given us, congratulations on the new release.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529529</id>
	<title>Re:Nuisances</title>
	<author>amicusNYCL</author>
	<datestamp>1246381200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>They've been talking about these changes for a long, long time.  If you're still using ereg, or register globals, or magic quotes, or whatever else you want to complain about them changing, then that's your problem.  If you have important code laying around that you haven't looked through yet, you might want to pencil that in.  There's no reason to have PHP4-only code sitting around these days.</p></htmltext>
<tokenext>They 've been talking about these changes for a long , long time .
If you 're still using ereg , or register globals , or magic quotes , or whatever else you want to complain about them changing , then that 's your problem .
If you have important code laying around that you have n't looked through yet , you might want to pencil that in .
There 's no reason to have PHP4-only code sitting around these days .</tokentext>
<sentencetext>They've been talking about these changes for a long, long time.
If you're still using ereg, or register globals, or magic quotes, or whatever else you want to complain about them changing, then that's your problem.
If you have important code laying around that you haven't looked through yet, you might want to pencil that in.
There's no reason to have PHP4-only code sitting around these days.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529203</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528555</id>
	<title>Would you let it die already?</title>
	<author>Anonymous</author>
	<datestamp>1246377540000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext><p>It's high time we forget about PHP and all it's bain-damaged design</p></htmltext>
<tokenext>It 's high time we forget about PHP and all it 's bain-damaged design</tokentext>
<sentencetext>It's high time we forget about PHP and all it's bain-damaged design</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530257</id>
	<title>Re:Looking Forward To It</title>
	<author>Anonymous</author>
	<datestamp>1246383360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It might put a roof over your head and food on the table, but lets face it, as a PHP dev you probably earn peanuts, and both the roof and food are of a shitty quality.</p><p>Myself, I use both Microsoft's MVC framework and Ruby on Rails, and earn so much money I don't know what to do with it all. I suggest you ditch PHP and learn something else.</p></htmltext>
<tokenext>It might put a roof over your head and food on the table , but lets face it , as a PHP dev you probably earn peanuts , and both the roof and food are of a shitty quality.Myself , I use both Microsoft 's MVC framework and Ruby on Rails , and earn so much money I do n't know what to do with it all .
I suggest you ditch PHP and learn something else .</tokentext>
<sentencetext>It might put a roof over your head and food on the table, but lets face it, as a PHP dev you probably earn peanuts, and both the roof and food are of a shitty quality.Myself, I use both Microsoft's MVC framework and Ruby on Rails, and earn so much money I don't know what to do with it all.
I suggest you ditch PHP and learn something else.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528597</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528751</id>
	<title>Re:features!</title>
	<author>vivaoporto</author>
	<datestamp>1246378380000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>GOTO has its uses. I never used it (as I prefer a more structured way to code), but critical mission error handling may take advantage of a more direct way to "jump".

Anyway, one excepcional addition to the language is <a href="http://php.net/closures" title="php.net">closures</a> [php.net]. Real anonymous functions were missing for a long time on the language, and it is great to have it now.

Now it is only a matter of our customers' hosting providers to update their versions of PHP. Oh, well, considering most just migrated from PHP 4 to 5 (thanks to the EOL last year), it may take some time.</htmltext>
<tokenext>GOTO has its uses .
I never used it ( as I prefer a more structured way to code ) , but critical mission error handling may take advantage of a more direct way to " jump " .
Anyway , one excepcional addition to the language is closures [ php.net ] .
Real anonymous functions were missing for a long time on the language , and it is great to have it now .
Now it is only a matter of our customers ' hosting providers to update their versions of PHP .
Oh , well , considering most just migrated from PHP 4 to 5 ( thanks to the EOL last year ) , it may take some time .</tokentext>
<sentencetext>GOTO has its uses.
I never used it (as I prefer a more structured way to code), but critical mission error handling may take advantage of a more direct way to "jump".
Anyway, one excepcional addition to the language is closures [php.net].
Real anonymous functions were missing for a long time on the language, and it is great to have it now.
Now it is only a matter of our customers' hosting providers to update their versions of PHP.
Oh, well, considering most just migrated from PHP 4 to 5 (thanks to the EOL last year), it may take some time.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528473</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530051</id>
	<title>Re:new features in php 5.3</title>
	<author>Anonymous</author>
	<datestamp>1246382820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The backslash name separator looks awful to me, although I've always found PHP code kind of garish with all the dollar signs and curly braces.  Although it's at least readable compared to some perl I've seen!</p><p>Looking at the "what's new" list I see the cool new feature of php archives.<nobr> <wbr></nobr>.phar files are zips or tarballs that can be included all at once in your program.  Seeing that brings up something I've always struggled with in PHP.  When should one use "include," "include\_once," "require," or "require\_once?"  Seems like include normally just inserts the included file into the current source code as if it was there to begin with, no?  I guess in the past without namespaces that's probably what most people needed most of the time.  And after converting my development wholesale to python with it's inherent namespaces (which are really just singleton objects bound to a local name), it seems like PHP's system is a bit convoluted.</p></htmltext>
<tokenext>The backslash name separator looks awful to me , although I 've always found PHP code kind of garish with all the dollar signs and curly braces .
Although it 's at least readable compared to some perl I 've seen ! Looking at the " what 's new " list I see the cool new feature of php archives .
.phar files are zips or tarballs that can be included all at once in your program .
Seeing that brings up something I 've always struggled with in PHP .
When should one use " include , " " include \ _once , " " require , " or " require \ _once ?
" Seems like include normally just inserts the included file into the current source code as if it was there to begin with , no ?
I guess in the past without namespaces that 's probably what most people needed most of the time .
And after converting my development wholesale to python with it 's inherent namespaces ( which are really just singleton objects bound to a local name ) , it seems like PHP 's system is a bit convoluted .</tokentext>
<sentencetext>The backslash name separator looks awful to me, although I've always found PHP code kind of garish with all the dollar signs and curly braces.
Although it's at least readable compared to some perl I've seen!Looking at the "what's new" list I see the cool new feature of php archives.
.phar files are zips or tarballs that can be included all at once in your program.
Seeing that brings up something I've always struggled with in PHP.
When should one use "include," "include\_once," "require," or "require\_once?
"  Seems like include normally just inserts the included file into the current source code as if it was there to begin with, no?
I guess in the past without namespaces that's probably what most people needed most of the time.
And after converting my development wholesale to python with it's inherent namespaces (which are really just singleton objects bound to a local name), it seems like PHP's system is a bit convoluted.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529171</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529357</id>
	<title>me first .. :)</title>
	<author>rs232</author>
	<datestamp>1246380660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>What feeture is PHP missing already, otherwise I would use it<nobr> <wbr></nobr>:)</htmltext>
<tokenext>What feeture is PHP missing already , otherwise I would use it : )</tokentext>
<sentencetext>What feeture is PHP missing already, otherwise I would use it :)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529235</id>
	<title>Re:Looking Forward To It</title>
	<author>TheRealMindChild</author>
	<datestamp>1246380240000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>0</modscore>
	<htmltext>PHP is the "new VB". Visual Basic had the stigma that anyone who touched it was a retard and anything produced by it would be retarded. But just like PHP, it was because people with no coding background started with it. It does a whole lot of complicated things for you AND you can still find ways to shoot yourself and coworkers in the face. Ultimately though, if you truly were competent, you could produce some solid work. It's like racism, only toward developers of language X.</htmltext>
<tokenext>PHP is the " new VB " .
Visual Basic had the stigma that anyone who touched it was a retard and anything produced by it would be retarded .
But just like PHP , it was because people with no coding background started with it .
It does a whole lot of complicated things for you AND you can still find ways to shoot yourself and coworkers in the face .
Ultimately though , if you truly were competent , you could produce some solid work .
It 's like racism , only toward developers of language X .</tokentext>
<sentencetext>PHP is the "new VB".
Visual Basic had the stigma that anyone who touched it was a retard and anything produced by it would be retarded.
But just like PHP, it was because people with no coding background started with it.
It does a whole lot of complicated things for you AND you can still find ways to shoot yourself and coworkers in the face.
Ultimately though, if you truly were competent, you could produce some solid work.
It's like racism, only toward developers of language X.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528597</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530863</id>
	<title>Namespaces</title>
	<author>Parker Lewis</author>
	<datestamp>1246384800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>OH-MY-GOD! Nobody complaining about the weird namespace separator!</htmltext>
<tokenext>OH-MY-GOD !
Nobody complaining about the weird namespace separator !</tokentext>
<sentencetext>OH-MY-GOD!
Nobody complaining about the weird namespace separator!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529137</id>
	<title>Re:Hooray fileinfo is standard!</title>
	<author>nedwidek</author>
	<datestamp>1246379820000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>1</modscore>
	<htmltext><p>PHP as I told a manager is useful because it is ubiquitous, not because it is perfect or even particularly good. At the time I worked on a derivative of GForge, which is a definite example of the horrors that can come from PHP projects.</p><p>This is also an original quote by me: "The beauty of PHP is that it is so simple even an idiot can program with it. The problem with PHP is that so many idiots do choose to program in it."</p><p>In my own hosting, I have the choice of using RoR, but the app must be manually redeployed if the server is restarted. So I use CakePHP instead because PHP will be instantly available.<nobr> <wbr></nobr>:P</p><p>5.3 should be cool, now I just need to start pestering my hosting providers about upgrading.</p></div>
	</htmltext>
<tokenext>PHP as I told a manager is useful because it is ubiquitous , not because it is perfect or even particularly good .
At the time I worked on a derivative of GForge , which is a definite example of the horrors that can come from PHP projects.This is also an original quote by me : " The beauty of PHP is that it is so simple even an idiot can program with it .
The problem with PHP is that so many idiots do choose to program in it .
" In my own hosting , I have the choice of using RoR , but the app must be manually redeployed if the server is restarted .
So I use CakePHP instead because PHP will be instantly available .
: P5.3 should be cool , now I just need to start pestering my hosting providers about upgrading .</tokentext>
<sentencetext>PHP as I told a manager is useful because it is ubiquitous, not because it is perfect or even particularly good.
At the time I worked on a derivative of GForge, which is a definite example of the horrors that can come from PHP projects.This is also an original quote by me: "The beauty of PHP is that it is so simple even an idiot can program with it.
The problem with PHP is that so many idiots do choose to program in it.
"In my own hosting, I have the choice of using RoR, but the app must be manually redeployed if the server is restarted.
So I use CakePHP instead because PHP will be instantly available.
:P5.3 should be cool, now I just need to start pestering my hosting providers about upgrading.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528427</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531389</id>
	<title>Re:Horray</title>
	<author>Ractive</author>
	<datestamp>1246386360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Well... it was modded funny, so it should be.</htmltext>
<tokenext>Well... it was modded funny , so it should be .</tokentext>
<sentencetext>Well... it was modded funny, so it should be.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529135</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28554359</id>
	<title>Re:new features in php 5.3</title>
	<author>greywire</author>
	<datestamp>1246475160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Unfortunately traits did not make it into 5.3.</p><p>Which sucks because I thought that was one the coolest new things.</p></htmltext>
<tokenext>Unfortunately traits did not make it into 5.3.Which sucks because I thought that was one the coolest new things .</tokentext>
<sentencetext>Unfortunately traits did not make it into 5.3.Which sucks because I thought that was one the coolest new things.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529171</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529171</id>
	<title>new features in php 5.3</title>
	<author>whoisthis</author>
	<datestamp>1246380000000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>see whats <a href="http://www.webdigi.co.uk/blog/2009/what-is-new-in-php-53-for-php-amateurs/" title="webdigi.co.uk" rel="nofollow">new in PHP 5.3</a> [webdigi.co.uk].
Namespaces, phar, Closures &amp; Lambdas, Functors, Traits,Magic functions. See link above for examples.</htmltext>
<tokenext>see whats new in PHP 5.3 [ webdigi.co.uk ] .
Namespaces , phar , Closures &amp; Lambdas , Functors , Traits,Magic functions .
See link above for examples .</tokentext>
<sentencetext>see whats new in PHP 5.3 [webdigi.co.uk].
Namespaces, phar, Closures &amp; Lambdas, Functors, Traits,Magic functions.
See link above for examples.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531961</id>
	<title>Re:Looking Forward To It</title>
	<author>Ant P.</author>
	<datestamp>1246388220000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>No, no no. PHP is the "new COBOL". It's a horrible language, but it's built up too much inertia to get rid of it or most of its backward-compatibility disasters.</p><p>If you want the new VB take a look at Ruby - a language that lets you bring any webserver to its knees in only 5 minutes and 10* lines of code, no experience required.</p><p>*plus 800000 lines of framework</p></htmltext>
<tokenext>No , no no .
PHP is the " new COBOL " .
It 's a horrible language , but it 's built up too much inertia to get rid of it or most of its backward-compatibility disasters.If you want the new VB take a look at Ruby - a language that lets you bring any webserver to its knees in only 5 minutes and 10 * lines of code , no experience required .
* plus 800000 lines of framework</tokentext>
<sentencetext>No, no no.
PHP is the "new COBOL".
It's a horrible language, but it's built up too much inertia to get rid of it or most of its backward-compatibility disasters.If you want the new VB take a look at Ruby - a language that lets you bring any webserver to its knees in only 5 minutes and 10* lines of code, no experience required.
*plus 800000 lines of framework</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529235</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528987</id>
	<title>Re:Hooray fileinfo is standard!</title>
	<author>plague3106</author>
	<datestamp>1246379280000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>0</modscore>
	<htmltext><p>Heh... is it still just inline scripting, or did they come up with embedable contorls, like Asp.net or the java equivolent?</p></htmltext>
<tokenext>Heh... is it still just inline scripting , or did they come up with embedable contorls , like Asp.net or the java equivolent ?</tokentext>
<sentencetext>Heh... is it still just inline scripting, or did they come up with embedable contorls, like Asp.net or the java equivolent?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528427</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528705</id>
	<title>Namespaces...about time!</title>
	<author>javacowboy</author>
	<datestamp>1246378140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The lack of namespaces in any programming language is a massive car wreck just waiting to happen.   I once spent a few days trying to resolve an issue with a web portal application with different components brought together where the issue was caused entirely by a function name collision.</p></htmltext>
<tokenext>The lack of namespaces in any programming language is a massive car wreck just waiting to happen .
I once spent a few days trying to resolve an issue with a web portal application with different components brought together where the issue was caused entirely by a function name collision .</tokentext>
<sentencetext>The lack of namespaces in any programming language is a massive car wreck just waiting to happen.
I once spent a few days trying to resolve an issue with a web portal application with different components brought together where the issue was caused entirely by a function name collision.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28552009</id>
	<title>Re:My best feature...</title>
	<author>raju1kabir</author>
	<datestamp>1246453260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>How could you jump into the middle of a loop or a switch statement? It doesn't make sense. Essential context is missing. They ruled that out for a good reason; it's like teleporting into a blender.</htmltext>
<tokenext>How could you jump into the middle of a loop or a switch statement ?
It does n't make sense .
Essential context is missing .
They ruled that out for a good reason ; it 's like teleporting into a blender .</tokentext>
<sentencetext>How could you jump into the middle of a loop or a switch statement?
It doesn't make sense.
Essential context is missing.
They ruled that out for a good reason; it's like teleporting into a blender.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528701</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529135</id>
	<title>Re:Horray</title>
	<author>Ash-Fox</author>
	<datestamp>1246379820000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>0</modscore>
	<htmltext><blockquote><div><p>So does this mean I should upgrade from PHP 3.2? Are there any incompatibilities with my existing code?</p><p>Maybe someone can look over my login script and tell me if this will work in PHP5?</p><blockquote><div><p> <tt>$query\_login="select * FROM user";<br>$result\_login = mysql\_query($query\_login) or die("Your passwrod is might be bad I think");<br>//$login\_check = mysql\_num\_rows($result\_login);<br>while($row=mysql\_fetch\_array($result\_login))<br>{<br>$username=$row["username"];<br>if ($username==$username1)<br>{<br>echo "";<br>echo "window.location.href='login\_error.php?rec=qq';";<br>echo "";<br>exit;<br>}<br>}</tt></p></div> </blockquote></div> </blockquote><p>I hope that code is a joke...</p></div>
	</htmltext>
<tokenext>So does this mean I should upgrade from PHP 3.2 ?
Are there any incompatibilities with my existing code ? Maybe someone can look over my login script and tell me if this will work in PHP5 ?
$ query \ _login = " select * FROM user " ; $ result \ _login = mysql \ _query ( $ query \ _login ) or die ( " Your passwrod is might be bad I think " ) ; // $ login \ _check = mysql \ _num \ _rows ( $ result \ _login ) ; while ( $ row = mysql \ _fetch \ _array ( $ result \ _login ) ) { $ username = $ row [ " username " ] ; if ( $ username = = $ username1 ) { echo " " ; echo " window.location.href = 'login \ _error.php ? rec = qq ' ; " ; echo " " ; exit ; } } I hope that code is a joke.. .</tokentext>
<sentencetext>So does this mean I should upgrade from PHP 3.2?
Are there any incompatibilities with my existing code?Maybe someone can look over my login script and tell me if this will work in PHP5?
$query\_login="select * FROM user";$result\_login = mysql\_query($query\_login) or die("Your passwrod is might be bad I think");//$login\_check = mysql\_num\_rows($result\_login);while($row=mysql\_fetch\_array($result\_login)){$username=$row["username"];if ($username==$username1){echo "";echo "window.location.href='login\_error.php?rec=qq';";echo "";exit;}}  I hope that code is a joke...
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528643</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528427</id>
	<title>Hooray fileinfo is standard!</title>
	<author>Anonymous</author>
	<datestamp>1246377180000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>1</modscore>
	<htmltext><p>Now I don't have to do a song and dance of ugly hacks to get what I need from a file on systems without the extention.</p><p>Oh wait, almost any PHP project eventually gets reduced to a song and dance of ugly hacks.</p></htmltext>
<tokenext>Now I do n't have to do a song and dance of ugly hacks to get what I need from a file on systems without the extention.Oh wait , almost any PHP project eventually gets reduced to a song and dance of ugly hacks .</tokentext>
<sentencetext>Now I don't have to do a song and dance of ugly hacks to get what I need from a file on systems without the extention.Oh wait, almost any PHP project eventually gets reduced to a song and dance of ugly hacks.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531095</id>
	<title>nt4</title>
	<author>Sicnarf</author>
	<datestamp>1246385460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>as of this version, windows nt 4 will no longer be supported<nobr> <wbr></nobr>:-(</htmltext>
<tokenext>as of this version , windows nt 4 will no longer be supported : - (</tokentext>
<sentencetext>as of this version, windows nt 4 will no longer be supported :-(</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529241</id>
	<title>Re:Horray</title>
	<author>Anonymous</author>
	<datestamp>1246380240000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Some kind of "daily WTF" troll, it seems.</p><p>OTOH, I can't imagine PHP article used for anything apart from trolling (like the Perl articles a while back, and Ruby articles one year from now).</p></htmltext>
<tokenext>Some kind of " daily WTF " troll , it seems.OTOH , I ca n't imagine PHP article used for anything apart from trolling ( like the Perl articles a while back , and Ruby articles one year from now ) .</tokentext>
<sentencetext>Some kind of "daily WTF" troll, it seems.OTOH, I can't imagine PHP article used for anything apart from trolling (like the Perl articles a while back, and Ruby articles one year from now).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528643</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531389
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528643
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529453
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528473
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530055
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529203
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530257
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528597
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529215
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528597
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529241
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528643
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28532059
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528751
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528473
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528827
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528555
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530483
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529203
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28532885
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531343
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528837
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528473
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530859
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528643
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28552009
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528701
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531961
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529235
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528597
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529137
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528427
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528427
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529821
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528427
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529901
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528643
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531365
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529203
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528673
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528473
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528427
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28554359
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529171
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28532013
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528643
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530051
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529171
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530119
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528643
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529529
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529203
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529845
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529203
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529351
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528705
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1425208_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28540483
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529203
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528597
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529215
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530257
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529235
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531961
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28537193
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528643
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529901
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530859
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529241
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529135
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530119
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531389
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28532013
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528471
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528701
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28552009
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528427
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531747
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529137
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528987
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529821
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531343
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28532885
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528705
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529351
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528473
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528751
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28532059
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528837
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529453
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528673
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529203
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28540483
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529845
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529529
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530055
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530483
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531365
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28529171
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28554359
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530051
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28531095
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528555
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28528827
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28530863
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1425208.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1425208.28536059
</commentlist>
</conversation>
