[PHP-DEV] Re: Changes in Sessions? (PHP Versions...)

2002-02-04 Thread Yasuo Ohgaki

Travis Simpson wrote:
 Hey,
 
 I am just wondering if there were any changes done to the session
 engine or settings between PHP 4.0.6 and 4.1.1.
 
 I have been getting nothing but grief from 4.0.6 and 4.1.1 seems to work
 fine.
 
 Any help would be MUCH appreciated.

You are asking to wrong list :)
Ask this kind of question to php-general.
I'm also reading the list and reply sometimes.

 
 Thanks,
 -Travis
 
 Oh, and where do I get PHP v.5? (Is it out for testing yet?)
 

In CVS, if you want.

-- 
Yasuo Ohgaki


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




[PHP-DEV] RE: changes

2001-04-11 Thread James Moore


  What are we doing with the current release right now?
  who is having problems and which problems are outstanding??

 a single compiler warning issue - in ext/standard/exec.h there must be a
 declaration of php_Exec:

 int php_Exec(int type, char *cmd, pval *array, pval *return_value);

People what do you think? does this need to be fixed? Im no compiler guru,
Sascha do you know you seem to have a pretty good idea of what compilers
will cope with what?

Cheers,

- James


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]




[PHP-DEV] RE: changes

2001-04-11 Thread Sascha Schumann

On Wed, 11 Apr 2001, James Moore wrote:


   What are we doing with the current release right now?
   who is having problems and which problems are outstanding??
 
  a single compiler warning issue - in ext/standard/exec.h there must be a
  declaration of php_Exec:
 
  int php_Exec(int type, char *cmd, pval *array, pval *return_value);

 People what do you think? does this need to be fixed? Im no compiler guru,
 Sascha do you know you seem to have a pretty good idea of what compilers
 will cope with what?

Every compiler should be able to cope with function calls to
functions without prototypes.  In this case, there should not
be problems regarding default argument promotions.

- Sascha Experience IRCG
  http://schumann.cx/http://schumann.cx/ircg


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]




[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] RE: changes

2001-04-11 Thread Sascha Schumann

 the idea is that it would be better if the line above is included in
 exec.h... of course it works without it but at least i am not happy with it
 this way.

You would be perfectly right, if we would be dealing with the
main branch of CVS.  In the case of the release branch, many
people consider changes to be "bad" per default.  So, if we
can release working code without applying any changes, we
usually prefer that route.

- Sascha Experience IRCG
  http://schumann.cx/http://schumann.cx/ircg


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]




[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] RE: changes

2001-04-11 Thread Boian Bonev

hi,

i am speaking for the main branch. if the community decides that adding a
function declaration can break anything then just do not commit this into
4.0.5 :)

as far as i have seen many major changes have been made to 4.0.5. anyway it
will work both ways except that calling the function with wrong args wont
issue a warning (at least for gcc - i have seen compilers pretending to be
more strict than needed and giving errors in such a condition).

btw. a month ago Rasmus asured me that the change is in cvs but perhapse he
has commited it to the wrong branch.

b.

  the idea is that it would be better if the line above is included in
  exec.h... of course it works without it but at least i am not happy with
it
  this way.

 You would be perfectly right, if we would be dealing with the
 main branch of CVS.  In the case of the release branch, many
 people consider changes to be "bad" per default.  So, if we
 can release working code without applying any changes, we
 usually prefer that route.



-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]