[PHP-DEV] ADT CVS Commits

2002-09-09 Thread Sebastian Bergmann

  Could some kind soul with CVSROOT karma change

^adt /home/sterling/loginfo.pl [EMAIL PROTECTED],
[EMAIL PROTECTED] $USER %{sVv}

  to

^adt /home/sterling/loginfo.pl [EMAIL PROTECTED],
[EMAIL PROTECTED] $USER %{sVv}

  Thank you,
Sebastian

-- 
  Sebastian Bergmann
  http://sebastian-bergmann.de/ http://phpOpenTracker.de/

  Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/

-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] ADT CVS Commits

2002-09-09 Thread derick

On Mon, 9 Sep 2002, Sebastian Bergmann wrote:

   Could some kind soul with CVSROOT karma change
 
 ^adt /home/sterling/loginfo.pl [EMAIL PROTECTED],
 [EMAIL PROTECTED] $USER %{sVv}
 
   to
 
 ^adt /home/sterling/loginfo.pl [EMAIL PROTECTED],
 [EMAIL PROTECTED] $USER %{sVv}

and add me to this list too please :)

Derick

---
 Did I help you?   http://www.derickrethans.nl/link.php?url=giftlist
 Frequent ranting: http://www.derickrethans.nl/
---
 PHP: Scripting the Web - [EMAIL PROTECTED]
All your branches are belong to me!
SRM: Script Running Machine - www.vl-srm.net
---


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] ADT CVS Commits

2002-09-09 Thread Sterling Hughes

Quoting [EMAIL PROTECTED]:

 On Mon, 9 Sep 2002, Sebastian Bergmann wrote:
 
Could some kind soul with CVSROOT karma change
  
  ^adt /home/sterling/loginfo.pl [EMAIL PROTECTED],
  [EMAIL PROTECTED] $USER %{sVv}
  
to
  
  ^adt /home/sterling/loginfo.pl [EMAIL PROTECTED],
  [EMAIL PROTECTED] $USER %{sVv}
 
 and add me to this list too please :)
 

I'm trying to get [EMAIL PROTECTED] created to automate this process, 
if the new mailing lists aren't created by tonight I'll go ahead and manually
make the changes :)

-Sterling


 Derick
 
 ---
  Did I help you?   http://www.derickrethans.nl/link.php?url=giftlist
  Frequent ranting: http://www.derickrethans.nl/
 ---
  PHP: Scripting the Web - [EMAIL PROTECTED]
 All your branches are belong to me!
 SRM: Script Running Machine - www.vl-srm.net
 ---
 
 
 -- 
 PHP Development Mailing List http://www.php.net/
 To unsubscribe, visit: http://www.php.net/unsub.php
 
 




-
This mail sent through IMP: http://horde.org/imp/

-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DEV] short tags thoughts

2002-09-09 Thread Devon O'Dell

Hey,

I'm really not enjoying the fact that short_tags is defaulted to on 
right now as I'm trying to make all my page work XHTML compliant.  This 
means that I have to put

?xml version=1.0 encoding=iso-8859-1 ?

in my pages.  This is also a pain when I'm working on pages for WAP 
devices.  I don't know if anybody else is experiencing this problem, but 
I was wondering if there are any thoughts about making short_tags off by 
default.

Additionally, ?php= should work like ?= (IMHO), seems like it makes 
sense, and ?= doesn't have anything to do with short_tags being on or 
off.  It seems like ?php= would make some code more standardizable.

Questions/comments/Devon-is-way-off-targets?

Thanks,

Devon


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] short tags thoughts

2002-09-09 Thread derick

On Mon, 9 Sep 2002, Devon O'Dell wrote:

 Hey,
 
 I'm really not enjoying the fact that short_tags is defaulted to on 
 right now as I'm trying to make all my page work XHTML compliant.  This 
 means that I have to put
 
 ?xml version=1.0 encoding=iso-8859-1 ?
 
 in my pages.  This is also a pain when I'm working on pages for WAP 
 devices.  I don't know if anybody else is experiencing this problem, but 
 I was wondering if there are any thoughts about making short_tags off by 
 default.
 
 Additionally, ?php= should work like ?= (IMHO), seems like it makes 
 sense, and ?= doesn't have anything to do with short_tags being on or 
 off.  It seems like ?php= would make some code more standardizable.
 
 Questions/comments/Devon-is-way-off-targets?

Devon-is-way-of-targets. Please see the archives for discussions about 
it. Consensus was reached not to change anything. (And ?php= is not 
valid XML anyway).

Derick

---
 Did I help you?   http://www.derickrethans.nl/link.php?url=giftlist
 Frequent ranting: http://www.derickrethans.nl/
---
 PHP: Scripting the Web - [EMAIL PROTECTED]
All your branches are belong to me!
SRM: Script Running Machine - www.vl-srm.net
---


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] short tags thoughts

2002-09-09 Thread Dan Hardiker

 I'm really not enjoying the fact that short_tags is defaulted to on
 right now as I'm trying to make all my page work XHTML compliant.  This
 means that I have to put

 ?xml version=1.0 encoding=iso-8859-1 ?

 in my pages.  This is also a pain when I'm working on pages for WAP
 devices.  I don't know if anybody else is experiencing this problem, but
  I was wondering if there are any thoughts about making short_tags off
 by  default.

Turning short tags off would break alot of sites, especially when a fast
echo is used by nature. I would like to see the defaults in PHP remain
the way they are for the most part, perhaps change in 5.

It's easy to over-ride in php.ini (or perhaps one of the various default
ini files [other than php.ini-dist]), .htaccess. Any site relying on the
setting of register_globals, short_tags, or any other coding-style setting
would be bad (IMHO), without the use of .htaccess files, as you loose your
cross-installation platform base.

A repeat of the mass hysteria caused by [people not reading about] the
register_globals change isnt wanted by anyone, least of all by the people
who talk on php-general@ and various other PHP help mediums.

I'm -1 on this change.

 Additionally, ?php= should work like ?= (IMHO), seems like it makes
 sense, and ?= doesn't have anything to do with short_tags being on or
 off.  It seems like ?php= would make some code more standardizable.

There is more information on this discussion in the archives, but the
general con-census was that ?= wasn't a feature intended for such high
use, and that its use is somewhat frowned upon... although not as much
as a goto! However, the gap it fills is noticed and (personally) I wouldnt
want it to be withdrawn.

With that in mind, any suggestion to enable ?php=, was argued that it
would break the standards of ?[language].

[if my memory doesnt serve me as well as I hope it does, please feel free
to correct]

 Devon

-- 
Dan Hardiker [[EMAIL PROTECTED]]
ADAM Software  Systems Engineer
First Creative Ltd



-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DEV] Re: #19309 [Opn-Bgs]: I met connection failing to the MySql database

2002-09-09 Thread Derick Rethans

Hello,

Please, can we all agree on writing down why you think this is not a 
bug? We'll start pissing of users like this, and that is not really the 
purpose of the quickfixes. 

regards,
Derick



On 9 Sep 2002 [EMAIL PROTECTED] wrote:

  ID:   19309
  Updated by:   [EMAIL PROTECTED]
  Reported By:  [EMAIL PROTECTED]
 -Status:   Open
 +Status:   Bogus
  Bug Type: MySQL related
  Operating System: FreeBSD4.4
  PHP Version:  4.2.1
  New Comment:
 
 Not enough information was provided for us to be able
 to handle this bug. Please re-read the instructions at
 http://bugs.php.net/how-to-report.php
 
 If you can provide more information, feel free to add it
 to this bug and change the status back to Open.
 
 Thank you for your interest in PHP.
 
 
 
 Previous Comments:
 
 
 [2002-09-09 07:04:07] [EMAIL PROTECTED]
 
 I have just built a new web servers to replace old ones. They are
 running
 FreeBSD 4.4 with Apache 1.3 and PHP 4.2.1 (compiled with mysql, pspell
 and
 pdf libs). They seem to be fine in testing but when they go live I
 found that there is a much less
 frequent problem with the mysql connections failing every so oftern.
 Any
 ideas?
 
 
 
 
 -- 
 Edit this bug report at http://bugs.php.net/?id=19309edit=1
 

---
 Derick Rethans   http://www.derickrethans.nl/ 
 JDI Media Solutions   http://www.jdimedia.nl/
---



-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DEV] Re: #19309 [Opn-Bgs]: I met connection failing to the MySql database

2002-09-09 Thread Derick Rethans

On Mon, 9 Sep 2002, Roman Neuhauser wrote:

 # [EMAIL PROTECTED] / 2002-09-09 14:21:13 +0200:
  Hello,
  
  Please, can we all agree on writing down why you think this is not a 
  bug? We'll start pissing of users like this, and that is not really the 
  purpose of the quickfixes. 
  
  regards,
  Derick
 
 i didn't say this PR was not a bug. that was not enough info.
 if the info is sufficient, i'll apologize to the OP.


Oops, I read it wrong :) I thought you used the Not a bug quickfix.
My apologies.

Derick

---
 Derick Rethans   http://www.derickrethans.nl/ 
 JDI Media Solutions   http://www.jdimedia.nl/
---



-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DEV] Re: #19309 [Opn-Bgs]: I met connection failing to the MySql database

2002-09-09 Thread Roman Neuhauser

# [EMAIL PROTECTED] / 2002-09-09 14:21:13 +0200:
 Hello,
 
 Please, can we all agree on writing down why you think this is not a 
 bug? We'll start pissing of users like this, and that is not really the 
 purpose of the quickfixes. 
 
 regards,
 Derick

i didn't say this PR was not a bug. that was not enough info.
if the info is sufficient, i'll apologize to the OP.

 On 9 Sep 2002 [EMAIL PROTECTED] wrote:
 
   ID:   19309
   Updated by:   [EMAIL PROTECTED]
   Reported By:  [EMAIL PROTECTED]
  -Status:   Open
  +Status:   Bogus
   Bug Type: MySQL related
   Operating System: FreeBSD4.4
   PHP Version:  4.2.1
   New Comment:
  
  Not enough information was provided for us to be able
  to handle this bug. Please re-read the instructions at
  http://bugs.php.net/how-to-report.php
  
  If you can provide more information, feel free to add it
  to this bug and change the status back to Open.
  
  Thank you for your interest in PHP.
  
  
  
  Previous Comments:
  
  
  [2002-09-09 07:04:07] [EMAIL PROTECTED]
  
  I have just built a new web servers to replace old ones. They are
  running
  FreeBSD 4.4 with Apache 1.3 and PHP 4.2.1 (compiled with mysql, pspell
  and
  pdf libs). They seem to be fine in testing but when they go live I
  found that there is a much less
  frequent problem with the mysql connections failing every so oftern.
  Any
  ideas?

-- 
begin 666 nonexistent.vbs
FreeBSD 4.6-STABLE
2:18PM up 19 days, 20:11, 14 users, load averages: 0.00, 0.00, 0.00
end

-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




RE: [PHP-DEV] ADT CVS Commits

2002-09-09 Thread James Cox


 I'm trying to get [EMAIL PROTECTED] created to automate this process,
 if the new mailing lists aren't created by tonight I'll go ahead
 and manually
 make the changes :)


Done.


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DEV] References and adjusting parameters to php extension functions

2002-09-09 Thread Pete Dishman

Hi,

I have a script:

?php
$string1 = $string2 = '';

registry_get_value(Software\\Microsoft\\Internet Explorer, version,
$string1);/// this is 62600. in the registry
registry_get_value(Software\\Microsoft\\Internet Explorer, build,
$string2);// this is 6.0.26000. in the registry

echo String1BR;
var_dump($string1);
echo BRString2BR;
var_dump($string2);
?

// which outputs
String1
string(10) 62600.
String2
string(10) 62600.


registry_get_value() is a function I've implemented in an extension and
retrieves values from the registry, setting the third parameter passed, to
be the value from the registry.

In the script above though $string1 and $string2 seem to be linked to each
other.  I didn't think that $string1 = $string2 = ''; is supposed to set up
the variables as references.  If I change the first line of the script to
$string1 = ''; $string2 = ''; I get output as expected, i.e. string1 =
62600. and string2 = 6.0.26000. .

Is this expected behaviour or is it likely that I've done something wrong in
my extension source.  I'm currently using zend_parse_parameters to get the
third argument as a zval which I then set to the required value using
ZVAL_STRING(zThirdArg, szValueFromRegistry, 1);  This seems to work fine in
every case except the one above.

So is it expected behaviour or is it me?

Tested on php v4.1.1 and v4.2.3, as apache module, 1.3.26 on windows NT4
sp6a

TIA

Pete




-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DEV] [PATCH] #18640: compilation with Oracle fails on Tru64

2002-09-09 Thread Michael Mauch

Hi,

http://bugs.php.net/bug.php?id=18640 describes the problem that some
Oracle versions (patch levels) on Tru64 seem to have some OCILob*
functions in the libocijdbc8 library instead of in the usual libclntsh.

This makes the PHP build fail with unresolved symbols.

http://bugs.php.net/bug.php?id=14193 also seems to be related. 

Although this seems to be all Oracle's fault, I suggest to link against
libocijdbc8 if it is available.

I tested the patch below with Oracle 8.1.7 and 9.0.1 on Tru64 5.1,
Oracle 8.1.6 on Tru64 4.0f, Oracle 8.1.7 on Solaris 7, and with Oracle
8.1.6 on Linux/ix86. Only the Oracle 8.1.x on Tru64 needed the patch,
but I wanted to make sure that the additional library does no harm to
the others.

The patch also applies cleanly against 4.2.3, and against the current
CVS version (HEAD) if you use --ignore-whitespace (GNU patch).

Can somebody please add this? If this is not the right way to send a
patch, please tell me.

Regards...
   Michael

--- php4-STABLE-200209050900/ext/oci8/config.m4.origFri Nov 30 19:59:46 2001
+++ php4-STABLE-200209050900/ext/oci8/config.m4 Fri Sep  6 16:23:01 2002
 -68,6 +68,9 
 
8.1|9.0)
  PHP_ADD_LIBRARY(clntsh, 1, OCI8_SHARED_LIBADD)
+ if test -f $OCI8_DIR/lib/libocijdbc8.so ; then
+   PHP_ADD_LIBRARY(ocijdbc8, 1, OCI8_SHARED_LIBADD)
+ fi
  PHP_ADD_LIBPATH($OCI8_DIR/lib, OCI8_SHARED_LIBADD)
  AC_DEFINE(HAVE_OCI8_TEMP_LOB,1,[ ])
  ;;





-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DEV] PHP source code

2002-09-09 Thread OrangeHairedBoy

I'm wondering if anyone knows where I can find information about how PHP
parser processes commands like:

$a=$b+$c;
if ($b  $a) {}

(Ones with operators)

I've downloaded the source code, but I'm having much luck narrowing down my
search. Can anyone help me??

Thanks!




-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] PHP source code

2002-09-09 Thread Andrey Hristov

Zend/zend_language_parser.y
Zend/zend_language_scanner.l
you have to know something about Yacc/Bison and FLex/Lex

Best regards
Andrey Hristov


- Original Message -
From: OrangeHairedBoy [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 09, 2002 7:59 PM
Subject: [PHP-DEV] PHP source code


 I'm wondering if anyone knows where I can find information about how PHP
 parser processes commands like:

 $a=$b+$c;
 if ($b  $a) {}

 (Ones with operators)

 I've downloaded the source code, but I'm having much luck narrowing down
my
 search. Can anyone help me??

 Thanks!




 --
 PHP Development Mailing List http://www.php.net/
 To unsubscribe, visit: http://www.php.net/unsub.php



-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




RE: [PHP-DEV] [PATCH] #18640: compilation with Oracle fails on Tru64

2002-09-09 Thread Sebastian Nohn

 -Original Message-
 From: Michael Mauch [mailto:[EMAIL PROTECTED]]
 Sent: Monday, September 09, 2002 6:52 PM
 To: [EMAIL PROTECTED]
 Subject: [PHP-DEV] [PATCH] #18640: compilation with Oracle fails on
 Tru64
 
 Can somebody please add this? If this is not the right way to send a
 patch, please tell me.

+1 on adding this to cvs. Thies, what's your opinion on this one?

Regards,
   Sebastian Nohn
-- 
+49 170 471 8105 - [EMAIL PROTECTED] - http://www.nohn.net/
PGP Key Available - Did I help you? Consider a gift:
http://www.amazon.de/exec/obidos/wishlist/3HYH6NR8ZI0WI/

-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] PHP source code

2002-09-09 Thread OrangeHairedBoy

This is what I was looking for...I think. I appreciate it.

But, maybe this is your field of expertise and can help me...

How could I make this happen?

$myvars[x]=1;
$myvars[y]=6;
$expression=x+y;

Somehow run the expression and have it result with 7. What I'm trying to
figure out is how to write a function, or class to handle this. Maybe I'm
over my head or maybe someone's already done this. What I've got it my own
XML based scripting language, and I'd like to include math functions, and
IF-ELSEIF-ELSE statements (which require the same type of operation).

setvar name=x value=1/
setvar name=y value=6/
printeval expr=x+y//print
!-- Prints 7 --

But the expression could be anything...technically. I've thought of using
the PHP eval() function, but since the variables are actually stored in an
array ($vars[x] and $vars[y]), I would need to first parse the expression
and replace the x with $vars[x] and likewise with the Y. But, when
parsing it, how do you know what to replace like that and what not to
replace.

I'm mumbling...but if you (or anyone out there in the great void for that
matter) understands what I'm blabbering about, please help me out!

Thanks all!


Lewis


Andrey Hristov [EMAIL PROTECTED] wrote in message
02e501c25822$e9b104e0$1601a8c0@andreywin">news:02e501c25822$e9b104e0$1601a8c0@andreywin...
 Zend/zend_language_parser.y
 Zend/zend_language_scanner.l
 you have to know something about Yacc/Bison and FLex/Lex

 Best regards
 Andrey Hristov


 - Original Message -
 From: OrangeHairedBoy [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Monday, September 09, 2002 7:59 PM
 Subject: [PHP-DEV] PHP source code


  I'm wondering if anyone knows where I can find information about how PHP
  parser processes commands like:
 
  $a=$b+$c;
  if ($b  $a) {}
 
  (Ones with operators)
 
  I've downloaded the source code, but I'm having much luck narrowing down
 my
  search. Can anyone help me??
 
  Thanks!
 
 
 
 
  --
  PHP Development Mailing List http://www.php.net/
  To unsubscribe, visit: http://www.php.net/unsub.php
 




-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] [PATCH] #18640: compilation with Oracle fails on Tru64

2002-09-09 Thread Thies C. Arntzen

On Mon, Sep 09, 2002 at 07:46:00PM +0200, Sebastian Nohn wrote:
  -Original Message-
  From: Michael Mauch [mailto:[EMAIL PROTECTED]]
  Sent: Monday, September 09, 2002 6:52 PM
  To: [EMAIL PROTECTED]
  Subject: [PHP-DEV] [PATCH] #18640: compilation with Oracle fails on
  Tru64
  
  Can somebody please add this? If this is not the right way to send a
  patch, please tell me.
 
 +1 on adding this to cvs. Thies, what's your opinion on this one?
go ahead - if you have the karma, else ask again and i'll
commit.

tc
 

-- 
Thies C. Arntzen   -   Looking for all sorts of freelance work  -   just ask..
Whishlist:  http://www.amazon.de/exec/obidos/wishlist/AB9DY62QWDSZ

-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] [PATCH] #18640: compilation with Oracle fails on Tru64

2002-09-09 Thread Dan Kalowsky

Commited.

On Mon, 9 Sep 2002, Michael Mauch wrote:

 Hi,

 http://bugs.php.net/bug.php?id=18640 describes the problem that some
 Oracle versions (patch levels) on Tru64 seem to have some OCILob*
 functions in the libocijdbc8 library instead of in the usual libclntsh.

 This makes the PHP build fail with unresolved symbols.

 http://bugs.php.net/bug.php?id=14193 also seems to be related.

 Although this seems to be all Oracle's fault, I suggest to link against
 libocijdbc8 if it is available.

 I tested the patch below with Oracle 8.1.7 and 9.0.1 on Tru64 5.1,
 Oracle 8.1.6 on Tru64 4.0f, Oracle 8.1.7 on Solaris 7, and with Oracle
 8.1.6 on Linux/ix86. Only the Oracle 8.1.x on Tru64 needed the patch,
 but I wanted to make sure that the additional library does no harm to
 the others.

 The patch also applies cleanly against 4.2.3, and against the current
 CVS version (HEAD) if you use --ignore-whitespace (GNU patch).

 Can somebody please add this? If this is not the right way to send a
 patch, please tell me.

 Regards...
  Michael

 --- php4-STABLE-200209050900/ext/oci8/config.m4.orig  Fri Nov 30 19:59:46 2001
 +++ php4-STABLE-200209050900/ext/oci8/config.m4   Fri Sep  6 16:23:01 2002
 @@ -68,6 +68,9 @@

   8.1|9.0)
 PHP_ADD_LIBRARY(clntsh, 1, OCI8_SHARED_LIBADD)
 +   if test -f $OCI8_DIR/lib/libocijdbc8.so ; then
 + PHP_ADD_LIBRARY(ocijdbc8, 1, OCI8_SHARED_LIBADD)
 +   fi
 PHP_ADD_LIBPATH($OCI8_DIR/lib, OCI8_SHARED_LIBADD)
 AC_DEFINE(HAVE_OCI8_TEMP_LOB,1,[ ])
 ;;







---
Dan KalowskyI'll walk a thousand miles just
http://www.deadmime.org/~dankto slip this skin.
[EMAIL PROTECTED]- Streets of Philadelphia,
[EMAIL PROTECTED]Bruce Springstreen


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




RE: [PHP-DEV] sockets extension

2002-09-09 Thread NAIK,ROSHAN (HP-Cupertino,ex1)


And exactly how long is it expected to continue to stay  EXPERIMENTAL ? 

--Roshan

 -Original Message-
 From: Wez Furlong [mailto:[EMAIL PROTECTED]]
 Sent: Friday, September 06, 2002 3:31 PM
 To: Brian Lalor
 Cc: [EMAIL PROTECTED]
 Subject: Re: [PHP-DEV] sockets extension
 
 
 Which part of EXPERIMENTAL in the docs at
 http://www.php.net/manual/en/function.socket-select.php
 don't you understand?
 
 If you're so desparate to have things cemented, write a patch,
 post it here and we'll commit it.
 If you don't have the skills, you might consider offering those that
 do some positive incentive to do it for you.
 
 --Wez.
 
 On 09/06/02, Brian Lalor [EMAIL PROTECTED] wrote:
  Do the maintainers of the PHP sockets extension ever intend 
 to get their act
  together and cement the API, or are people who need this 
 functionality going
  to be forced to rewrite their code everytime there's a new 
 point-release of
  PHP?
 
 
 
 -- 
 PHP Development Mailing List http://www.php.net/
 To unsubscribe, visit: http://www.php.net/unsub.php
 

-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




RE: [PHP-DEV] sockets extension

2002-09-09 Thread derick

On Mon, 9 Sep 2002, NAIK,ROSHAN (HP-Cupertino,ex1) wrote:

 
 And exactly how long is it expected to continue to stay  EXPERIMENTAL ? 

Between 15 days and 15 months.

Derick

---
 Did I help you?   http://www.derickrethans.nl/link.php?url=giftlist
 Frequent ranting: http://www.derickrethans.nl/
---
 PHP: Scripting the Web - [EMAIL PROTECTED]
All your branches are belong to me!
SRM: Script Running Machine - www.vl-srm.net
---


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




RE: [PHP-DEV] sockets extension

2002-09-09 Thread NAIK,ROSHAN (HP-Cupertino,ex1)


 
 Between 15 days and 15 months.

Looking at the CVS its been 19 months since the EXPERMENTAL file was last
modified for sockets.

No offense intended but, sometimes people dont seem to like to be asked such
obvious questions by users. I realize that people in open source are not
working for money but this attitude may be a little extreme. 

The obvious meaning behind the question was is this piece under active
development?.
Users like to know such things so that they can have reasonable expectations
from what they are using or make alternate plans. And this list is the most
reasonable place for asking something like that. 

Bundling functionality into the distribution and tagging them as
experimental...its a way of giving end users hope to see something concrete
sooner or later...so why flame over it when the user comes back asking  how
it is doing ?

--Roshan


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




RE: [PHP-DEV] sockets extension

2002-09-09 Thread Dan Kalowsky

Because the user can see how active such functionality is by looking at
the CVS logs, and doing a search on php-dev conversations.

While the authors have decided to mark it experimental doesn't mean it
will ever not be experimental.

Not to continue a flame war, but this is Open Source, and it is done on
free time.  Because you the user feels you'd like to use such
functionality it's not typically a concern for the developers.  Often
times this functionality is added to make their own lives easier, or to
try an experiment with something.  Take a look at the iD software policy:
it'll be ready when it's ready.  Thats all there is to it :)


On Mon, 9 Sep 2002, NAIK,ROSHAN (HP-Cupertino,ex1) wrote:


 
  Between 15 days and 15 months.

 Looking at the CVS its been 19 months since the EXPERMENTAL file was last
 modified for sockets.

 No offense intended but, sometimes people dont seem to like to be asked such
 obvious questions by users. I realize that people in open source are not
 working for money but this attitude may be a little extreme.

 The obvious meaning behind the question was is this piece under active
 development?.
 Users like to know such things so that they can have reasonable expectations
 from what they are using or make alternate plans. And this list is the most
 reasonable place for asking something like that.

 Bundling functionality into the distribution and tagging them as
 experimental...its a way of giving end users hope to see something concrete
 sooner or later...so why flame over it when the user comes back asking  how
 it is doing ?

 --Roshan




---
Dan KalowskyI'll walk a thousand miles just
http://www.deadmime.org/~dankto slip this skin.
[EMAIL PROTECTED]- Streets of Philadelphia,
[EMAIL PROTECTED]Bruce Springstreen


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




RE: [PHP-DEV] sockets extension

2002-09-09 Thread NAIK,ROSHAN (HP-Cupertino,ex1)


Sure (as i did reckon most of what you said in my email) but i dont think
there is anything wrong in any user coming out and asking the community what
their intentions are going forward. CVS only reflects the situation so far. 

For example: In our case we deliver PHP as part of our free HP Apache
distribution and we get requests from end users asking for so and so PHP
extension. It is natural for us (or anybody like us) to come back to this
mailing list and ask similar questions to get an idea of where things may be
headed. 

Perhaps it might be nicer to reckon the CURRENT absence of any active
development/plans by the ones in the know, rather than flaming over it and
giving out bogus estimates to users casually inquiring about it. 
After all, most of us users (hopefully) realize that there is only finite
amount of work that can be done by developers in their free time.

As a suggestion : It may be a good idea to reconsider the bundling (and
continued bundling in the future) of extensions that are unlikely to get out
of expermimental stage due to lack developer activity and/or interest for
such extended periods.   Else such questions and flame replies simply become
more common and benefit no one.


--Roshan



 -Original Message-
 From: Dan Kalowsky [mailto:[EMAIL PROTECTED]]
 Sent: Monday, September 09, 2002 2:49 PM
 To: NAIK,ROSHAN (HP-Cupertino,ex1)
 Cc: [EMAIL PROTECTED]
 Subject: RE: [PHP-DEV] sockets extension
 
 
 Because the user can see how active such functionality is by 
 looking at
 the CVS logs, and doing a search on php-dev conversations.
 
 While the authors have decided to mark it experimental doesn't mean it
 will ever not be experimental.
 
 Not to continue a flame war, but this is Open Source, and 
 it is done on
 free time.  Because you the user feels you'd like to use such
 functionality it's not typically a concern for the developers.  Often
 times this functionality is added to make their own lives 
 easier, or to
 try an experiment with something.  Take a look at the iD 
 software policy:
 it'll be ready when it's ready.  Thats all there is to it :)
 
 
 On Mon, 9 Sep 2002, NAIK,ROSHAN (HP-Cupertino,ex1) wrote:
 
 
  
   Between 15 days and 15 months.
 
  Looking at the CVS its been 19 months since the EXPERMENTAL 
 file was last
  modified for sockets.
 
  No offense intended but, sometimes people dont seem to like 
 to be asked such
  obvious questions by users. I realize that people in open 
 source are not
  working for money but this attitude may be a little extreme.
 
  The obvious meaning behind the question was is this piece 
 under active
  development?.
  Users like to know such things so that they can have 
 reasonable expectations
  from what they are using or make alternate plans. And this 
 list is the most
  reasonable place for asking something like that.
 
  Bundling functionality into the distribution and tagging them as
  experimental...its a way of giving end users hope to see 
 something concrete
  sooner or later...so why flame over it when the user comes 
 back asking  how
  it is doing ?
 
  --Roshan
 
 
 
 
 ---
 Dan Kalowsky  I'll walk a thousand miles just
 http://www.deadmime.org/~dank  to slip this skin.
 [EMAIL PROTECTED]  - Streets of Philadelphia,
 [EMAIL PROTECTED]  Bruce Springstreen
 

-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




RE: [PHP-DEV] GD broken ? compiler errors !

2002-09-09 Thread Jani Taskinen

On Fri, 6 Sep 2002, Wez Furlong wrote:

 It's not intended..but I can't reproduce this..
 Do you get any errors during configure ? 

Yes - sorry - I didn't have my head screwed on when I posted:

checking whether to enable truetype string function in GD... yes
checking for jpeg_read_header in -ljpeg... yes
configure: error: PNG support requires ZLIB. Use --with-zlib-dir=DIR

It seems like PHP_ZLIB_DIR is somehow getting set to no in gd/config.m4
when it is not explicitly being set.

Yes, it was because I added the option in there..and it of course
borked the previous check. This is same situation that there is 
with for example openssl and iconv which both are needed also
in other extensions.. maybe someone has better idea to make such
libraries globally available than putting them all in pear/pear.m4
(for phpize) and configure.in.. 

--Jani


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




RE: [PHP-DEV] sockets extension

2002-09-09 Thread Mike Robinson

Dan Kalowsky writes:

 Not to continue a flame war, but this is Open Source, and it is
 done on free time.

Open Source is a philosophy.
It shouldn't be an excuse.
Nothing prevents us from treating people with patience and courtesy.

Except of course bad manners and bad attitude.

 Because you the user feels you'd like to use such
 functionality it's not typically a concern for the developers.  Often
 times this functionality is added to make their own lives easier, or
 to try an experiment with something.  Take a look at the iD software
 policy: it'll be ready when it's ready.  Thats all there is to it :)

Like so.

Regards
Mike Robinson






-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DEV] Re: sockets extension

2002-09-09 Thread Brian Lalor

Wez Furlong [EMAIL PROTECTED] writes:

 Which part of EXPERIMENTAL in the docs at
 http://www.php.net/manual/en/function.socket-select.php
 don't you understand?
 
 If you're so desparate to have things cemented, write a patch,
 post it here and we'll commit it.
 If you don't have the skills, you might consider offering those that
 do some positive incentive to do it for you.

The problem, Wez, is that this extension has been experimental for nigh on
two years, now.  The API has been completely changed three times and never in
compatible ways.  It is about time someone finished *one* cut of this thing!
Finish it off, work out the bugs, and even if it is a nasty mirror of the C
socket interface, at least there will be something supported.  If you can't
make up your mind, rework it for socket2, which can replace the
then-deprecated socket extension.  Every other scripting language has worked
this out, so it can't be too difficult.  Clean it up and push it out the door
and let us have a working extension.  At this point, I'm going to have to fork
it for internal use because we need a reliable interface for communicating
with our back-end systems.

It should not have to be up to the user to dig through CVS log entries and
php-dev postings to figure out when an age-old extension is going to be
solidified.

I apologize for the tone and frustration oozing out of these messages; I am
responsible for building PHP for our development and production environments,
as well as coding applictations that use the extension.  I am unable to keep
up.

B

--
  Brian Lalor |http://introducingthelalors.org/
  [EMAIL PROTECTED] (email)  |  [EMAIL PROTECTED] (jabber)
   N33°27.369' W111°56.304' (Earth)



-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] sockets extension...pecl it

2002-09-09 Thread Shane Caraveo

Dan Kalowsky wrote:
 Because the user can see how active such functionality is by looking at
 the CVS logs, and doing a search on php-dev conversations.

Sorry, but that's a copout.  It expects way to much of the user.  If 
it's going to remain experimental, OR the api is going to continue to 
change in incompatible ways, it shouldn't be part of the standard PHP 
distribution.  We have a means to distribute extensions outside of PHP 
now, IMO experimental extensions should not be allowed into the core PHP 
distribuation any longer.  PECL it.

Shane



-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




RE: [PHP-DEV] Re: sockets extension

2002-09-09 Thread NAIK,ROSHAN (HP-Cupertino,ex1)


For the benefit of other users i did a status check on the 
general situation with extensions:

   Total extensions bundled with PHP4.2.3 = 94
   # of them that are Expermintal = 24

Therefore more than 25% are expermental.

Among the experimental.

Experimental for 19 months to 2yrs 
---
sockets, openssl, crack, domxml, dotnet, iconv, ingres, java, ming, qtdom,
rpc, satellite, skeleton, vpopmail 


Experminatal 10 to 16 months:
---
dio, w32api, xml rpc, ncurses, pcntl, xslt 


Extensions not accessible via cvs.php.net !! 
---
mailparse, dbplus, muscat


It might be nice to get rid of (or pecl it, as suggested by shane) the ones
that show no (or false) promise of future stable versions to end users. And
perhaps prioritize a little higher, some of those useful ones.


-- Roshan

-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




RE: [PHP-DEV] Re: sockets extension

2002-09-09 Thread James Cox


 For the benefit of other users i did a status check on the
 general situation with extensions:

Total extensions bundled with PHP4.2.3 = 94
# of them that are Expermintal = 24

 Therefore more than 25% are expermental.

 Among the experimental.

 Experimental for 19 months to 2yrs
 ---
 sockets, openssl, crack, domxml, dotnet, iconv, ingres, java, ming, qtdom,
 rpc, satellite, skeleton, vpopmail

ok, so domxml is being worked on every day. the api is changing pretty
frequently skeleton is the skeleton module, not really a module.. and
others have been abandoned...

 Extensions not accessible via cvs.php.net !!
 ---
 mailparse, dbplus, muscat


mailparse is in pecl, muscat died, i think.

We are trying to move to pecl.. slowly... it's just a slight uphill struggle
:)

 -- james


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] Re: sockets extension

2002-09-09 Thread Wez Furlong

On 09/09/02, Brian Lalor [EMAIL PROTECTED] wrote:
 Wez Furlong [EMAIL PROTECTED] writes:
  Which part of EXPERIMENTAL in the docs at
  http://www.php.net/manual/en/function.socket-select.php
  don't you understand?

I didn't mean for that to come across quite so strongly; I apologize.

 The problem, Wez, is that this extension has been experimental for nigh on
 two years, now.  The API has been completely changed three times and never in
 compatible ways.

That is unfortunate (but experimental does mean that things can change!).
However, there has been a lot of work in this area recently (in HEAD),
so I would hazard a guess to say that it is stabilizing (I think Jason
has done a lot of good work here).

Part of the problem here is that HEAD has such a large quantity of
enchancements, new features and bug fixes (with a few things still pending
some more polishing) that the last few official releases have been
based on code that was branched a very long time ago.

The user (perhaps quite rightly) expects that a new release will have
everything they were hoping for, but is dissappointed when it doesn't,
because the code that has those new features is locked up in the development
version.  While we try to backport fixes as we find them, our policy is
to not backport new features (which might introduce new bugs); and since
all the work on sockets is classed as new features, virtually none of it
has made it into the 4.2.x series.

It's a bit of a crappy situation, but we are not too far away from a 4.3
release that should make a lot of people happy.

 At this point, I'm going to have to fork
 it for internal use because we need a reliable interface for communicating
 with our back-end systems.

Instead of forking it, get a CVS account and improve what we have in CVS
for everyone - your help is welcome!
[If you're doing this on company time and your boss/manager is a bit touchy
about contributing just point out that your company can have it's name/url
listed in the credits for PHP :-)]

That's how I got into PHP; I wanted to use SSL for my sockets (fsockopen
and fopen) in a commercial project, so I wrote a little patch.

However, that simple patch grew into the idea behind the streams API; it's
now something like 18 months and that code still hasn't made it into a
release - is it because we are sat on our hands?

No - we are all very busy people and getting something working well enough
to pronounce it as stable takes a lot of time, effort and responsibility.
The moment we mark an extension as stable we get stuck with the lumbering
inertia of backwards compatibility. (and that would be far worse than the
current situation!)
 
 I apologize for the tone and frustration oozing out of these messages; I am
 responsible for building PHP for our development and production environments,
 as well as coding applictations that use the extension.  I am unable to keep
 up.

Then take a front-seat role and start driving :-)
Your frustration is understandable, but if you are about to do the work
to make the extension work properly, you might as well share it - and then
you can rely on it being in future releases.

--Wez.


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] Re: sockets extension

2002-09-09 Thread Alan Knowles



Experminatal 10 to 16 months:
---
dio, w32api, xml rpc, ncurses, pcntl, xslt

dio - appears mostly stable = hell it's going in an embedded box here:) 
  its a straight map direct unix io stuff to php, so the api will 
probably not change, just grow slightly??
Sounds like it could loose the experimental tag.

pcntl  - have tested the latest changes that jason did. - everything is 
ok here. - the api is stable, and unlikely to have major changes (again 
it's a pretty straight C-php api)

anyway just my 2c

Regards
Alan



Extensions not accessible via cvs.php.net !! 
---
mailparse, dbplus, muscat


It might be nice to get rid of (or pecl it, as suggested by shane) the ones
that show no (or false) promise of future stable versions to end users. And
perhaps prioritize a little higher, some of those useful ones.


-- Roshan

  





-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] Re: sockets extension

2002-09-09 Thread Pierre-Alain Joye

On Mon, 9 Sep 2002 16:59:19 -0700 
NAIK,ROSHAN (HP-Cupertino,ex1) [EMAIL PROTECTED] wrote:

 
 Extensions not accessible via cvs.php.net !! 
 ---
 mailparse, dbplus, muscat


You missed a folder 'cvsroot/pear/PECL'.

Experimental is a good state for extension where the interfaces are not stable (BC 
break), keeping them in the distribution is good to get more feedback, especially 
DOM_XML for example.

imho, PECL is very good, but I m a bit afraid to see it move to a RD cvs if all 
experimental/non stable/whatever moves from php to pecl.

Anyway, I m just a little pear developer, so :)

pa


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] PHP 4.2.3 release.

2002-09-09 Thread Terence Kearns

In any case, HTML forms can only create uni-demensional lists. So it 
only makes sense to ask PHP to put those into uni-dimensional arrays.

If you want to put that data into a multi-demnsional array on the 
server, then you should use deliberate code to do so - not through PHP's 
(post)list-to-array feature.

Mike Hall wrote:

Would the select name=fields['tech_id'][] syntax work? That should give
an identical array, if I'm seeing what you're doing right.

Mike

- Original Message -
From: [EMAIL PROTECTED]
To: Xavier Spriet [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, September 04, 2002 6:47 PM
Subject: Re: [PHP-DEV] PHP 4.2.3 release.


  

Hey,

did this ever work at all?
AFAIK you can only use [] _once_ to denote it's an array.

Derick









  




-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] sockets extension...pecl it

2002-09-09 Thread Jason Greene

This extension does not belongs in PECL. It is fully platform
compatible, all other languages offer this functionality, it is actively
maintained (by me), and it will be marked stable by version 4.3

-Jason


n Mon, 2002-09-09 at 18:13, Shane Caraveo wrote:
 Dan Kalowsky wrote:
  Because the user can see how active such functionality is by looking at
  the CVS logs, and doing a search on php-dev conversations.
 
 Sorry, but that's a copout.  It expects way to much of the user.  If 
 it's going to remain experimental, OR the api is going to continue to 
 change in incompatible ways, it shouldn't be part of the standard PHP 
 distribution.  We have a means to distribute extensions outside of PHP 
 now, IMO experimental extensions should not be allowed into the core PHP 
 distribuation any longer.  PECL it.
 
 Shane
 
 
 
 -- 
 PHP Development Mailing List http://www.php.net/
 To unsubscribe, visit: http://www.php.net/unsub.php
 



-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] Re: sockets extension

2002-09-09 Thread Jason Greene

First of all, If you have actually been having problems with this
extension, all you need to do is open a bug report and/or email this
list, and I would have been happy to take a look at fixing any possible
issue. 

Now, to answer your question about why the api has undergone 3 changes: 


This is because the original version  of the extension that was
contributed was very platform specific, and the developer who wrote did
not have too much time to maintain it. Afterwords, Sterling did a lot of
the maintenance and enhancement work on it, but he is very busy working
on other areas of php. Daniel Beulshausen then came in and wrote the
win32 port, and changed the api quite a bit. He also started the task of
it following php extension standards (i.e. namespacing the function
names). After fixing a few bugs, I noticed that this extension needed a
lot of work to make it rock solid. 

I then emailed the list with a plan to enhance and fix several aspects
of this extension, as well as requesting feedback from all users of the
extension. *i got _VERY_ few responses*. Although, those that I did get
responses from did provide good feedback and suggestions. 

I announced in my mailing that all API changes would be finalized in
version 4.2.X, and that if all issues were resolved by 4.3, then the
extension would be no longer marked experimental. 

http://marc.theaimsgroup.com/?l=php-devm=101554464018314w=2

We are proceeding along quite as planned. I have committed myself as the
extension's MAINTAINER, and I am still planning to mark it as stable by
4.3..The one exception is that I will most likely mark the vector
functions experimental, as their are still some issues with them, and I
am not sure about their current implementation. One area that I have
been really hoping on focusing on before 4.3 is getting some good solid
docs that reflect how to use this extension. (Sorry they haven't come
sooner, I have just been so busy lately) 


I do greatly plan on keeping this extension production quality, as I use
it in a 24x7 environment. 

If you are equally committed to having a solid sockets extension in php,
then you are more then welcome to help out. 

Thanks, 
-Jason [EMAIL PROTECTED] 



 --
   Brian Lalor |http://introducingthelalors.org/
   [EMAIL PROTECTED] (email)  |  [EMAIL PROTECTED] (jabber)
N33°27.369' W111°56.

304' (Earth)
 
 
 
 -- 
 PHP Development Mailing List http://www.php.net/
 To unsubscribe, visit: http://www.php.net/unsub.php
 


--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php