On Wed, 9 May 2001, Sterling Hughes wrote:
On Thu, 10 May 2001, Jani Taskinen wrote:
This is just because some developers don't like to follow the guidelines.
As, I quote, it woulnd't be fun anymore or you can't force anyone.
Hrrmmm.. Which guidelines would those be? And no, you can't force
On Thu, 10 May 2001, Jani Taskinen wrote:
On Wed, 9 May 2001, Sterling Hughes wrote:
On Thu, 10 May 2001, Jani Taskinen wrote:
This is just because some developers don't like to follow the guidelines.
As, I quote, it woulnd't be fun anymore or you can't force anyone.
Hrrmmm.. Which
At 06:46 10/5/2001, Harald Radi wrote:
looking forward to getting php case sensitive i'm just wondering that
function names are exported mixed case in the com extension.
e.g. there's a COM_load() and a com_set(), is there a special reason for
this (zeev) ?
There's no special reason, and it's
Sterling Hughes [EMAIL PROTECTED] schrieb im Newsbeitrag
news:[EMAIL PROTECTED]...
On Thu, 10 May 2001, Jani Taskinen wrote:
On Wed, 9 May 2001, Sterling Hughes wrote:
On Thu, 10 May 2001, Jani Taskinen wrote:
This is just because some developers don't like to follow the
guidelines.
On Thu, 10 May 2001, Harald Radi wrote:
looking forward to getting php case sensitive i'm just wondering that
Me too.
function names are exported mixed case in the com extension.
e.g. there's a COM_load() and a com_set(), is there a special reason for
this (zeev) ?
This is just because some
On Thu, 10 May 2001, Jani Taskinen wrote:
On Thu, 10 May 2001, Harald Radi wrote:
looking forward to getting php case sensitive i'm just wondering that
Me too.
function names are exported mixed case in the com extension.
e.g. there's a COM_load() and a com_set(), is there a special
