At 03:04 28.03.2003, Andi Gutmans wrote:
At 10:43 PM 3/27/2003 +0100, Marcus Börger wrote:
At 19:13 27.03.2003, Andi Gutmans wrote:
At 06:55 PM 3/27/2003 +0100, Timm Friebe wrote:
On Thu, 2003-03-27 at 18:45, Brian Moon wrote:
> Ok, sorry, I have been off the ZE2 list for a while (just joined back)
At 08:43 28.03.2003, Manuel Lemos wrote:
Hello,
I have not had time to look this in detail so I could not reach a conclusion.
Is the upcoming object model supporting package level member access
retrictions like in Java?
For those that are not aware of what is that, packages are a group of
inde
The point is that we don't raise an E_ERROR when you pass the wrong type
of parameter to any of the other PHP functions.
A "real" programmer is not a Java (*spit!*) programmer; it is someone
that wants to make their code as robust as possible.
Again, I will use the idea of a SOAP server implement
On Fri, 2003-03-28 at 11:04, Wez Furlong wrote:
> Using E_ERROR also prohibits using CLI or embedded PHP in a long-lived
> application. I know that PHP is designed primarily for use in a web
> server, but it seems incredibly short sighted to design new features
> that make using CLI or embed impos
That's a known issue.
See http://bugs.php.net/bug.php?id=22215
Moriyoshi
Sebastian Bergmann <[EMAIL PROTECTED]> wrote:
> Building PHP with bison versions up to 1.75 works fine, but both
> bison 1.875 and 1.875a cause a segfault during the startup of PHP.
--
PHP Internals - PHP Runtime De
Moriyoshi Koizumi wrote:
> That's a known issue.
I know.
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/
--
PHP Internals - PHP Runtime Development Mailing List
To uns
I have no problem with renaming our empty_string to zend_empty_string.
The only problem is that it breaks the API. What do people think?
I'm also considering removing empty_string completely but I still need to
look through all of the code and try to evaluate the performance change due
to it (We
Not offending.. I should have read mails more carefully. And I hope
bison guys would give us some worthy information on this issue.
Moriyoshi
Sebastian Bergmann <[EMAIL PROTECTED]> wrote:
> Moriyoshi Koizumi wrote:
> > That's a known issue.
>
> I know.
>
> --
> Sebastian Bergmann
> htt
Help in the translating of the docs in portuguese from Brazil.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Class for manage a session. It works with php 4.3.x but not with PHP5
(cvs every day).
Note the read_session() function.
bye
";
}
class zb_session
{
var $dbms;
var $session_exist;
var $session_close = false;
function __construct()
{
zb_debug("Sono nel costruttore")
I am not seeing this problem with Apache 1.3, PHP_4_3 or php5-HEAD and
tru64, nor with the cli.
What platform are you seeing it on ? Could it be any unitilized or buffer
overflow issue ?
Dave
- Original Message -
From: "Sebastian Bergmann" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent:
This again gets to my nit regarding runtime features in a dynamically
typed language. One of the reasons type checking in C, C++, Java is a
good thing is its done at compile time, not runtime. Type mistakes,
especially in large libraries can be pesky things, often hard to check
for (and often har
We won't support this. (btw it's the default modifier in Java if you don't
write anything else).
Andi
At 04:43 AM 3/28/2003 -0300, Manuel Lemos wrote:
Hello,
I have not had time to look this in detail so I could not reach a conclusion.
Is the upcoming object model supporting package level memb
At 10:04 AM 3/28/2003 +, Wez Furlong wrote:
The point is that we don't raise an E_ERROR when you pass the wrong type
of parameter to any of the other PHP functions.
Really? I think that some functions which use resources do error out if you
pass a wrong type (although I'm not quite sure), but
On Fri, 28 Mar 2003, Andi Gutmans wrote:
> At 10:04 AM 3/28/2003 +, Wez Furlong wrote:
> >The point is that we don't raise an E_ERROR when you pass the wrong type
> >of parameter to any of the other PHP functions.
>
> Really? I think that some functions which use resources do error out if you
At 08:42 AM 3/28/2003 -0500, Sterling Hughes wrote:
This again gets to my nit regarding runtime features in a dynamically
typed language. One of the reasons type checking in C, C++, Java is a
good thing is its done at compile time, not runtime. Type mistakes,
especially in large libraries can be
On Fri, 2003-03-28 at 09:15, Andi Gutmans wrote:
> At 08:42 AM 3/28/2003 -0500, Sterling Hughes wrote:
> >This again gets to my nit regarding runtime features in a dynamically
> >typed language. One of the reasons type checking in C, C++, Java is a
> >good thing is its done at compile time, not ru
On Fri, 28 Mar 2003, Sterling Hughes wrote:
> Pah, we all know the future is psp
> (http://www.edwardbear.org/mod_psp-0.3.tar.gz ;-)
>
> Just to be clear: I'd be happier without type hinting then type hinting
> throwing an E_ERROR (a E_WARNING would also make me happy).
I agree 100% here.
Deric
At 08:59 AM 3/28/2003 -0500, Sterling Hughes wrote:
Pah, we all know the future is psp
(http://www.edwardbear.org/mod_psp-0.3.tar.gz ;-)
psp sucks badly :P
Just to be clear: I'd be happier without type hinting then type hinting
throwing an E_ERROR (a E_WARNING would also make me happy).
The proble
At 03:19 PM 3/28/2003 +0100, Derick Rethans wrote:
On Fri, 28 Mar 2003, Sterling Hughes wrote:
> Pah, we all know the future is psp
> (http://www.edwardbear.org/mod_psp-0.3.tar.gz ;-)
>
> Just to be clear: I'd be happier without type hinting then type hinting
> throwing an E_ERROR (a E_WARNING wou
David Hill wrote:
> What platform are you seeing it on?
Linux.
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/
--
PHP Internals - PHP Runtime Development Mailing List
Andi Gutmans wrote:
> OK so maybe we should go ahead and nuke it and save us the argument.
Please, no.
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/
--
PHP Internals
On Fri, 28 Mar 2003, Andi Gutmans wrote:
> The point of type-hints is to be able to catch errors in your code
> quickly and not having to write checks, the point isn't to catch
> problems in your code at run-time. And as I said before, if it doesn't
> suite you then don't use type-hints and use i
At 03:56 PM 3/28/2003 +0100, Sebastian Bergmann wrote:
Andi Gutmans wrote:
> OK so maybe we should go ahead and nuke it and save us the argument.
Please, no.
The main problem is that people are getting carried away and instead of
looking at the big step forward the OOP model has done since PHP 4
Andi Gutmans wrote:
> I say nuke type-hints and let the purists use instanceof.
I know that Type Hints are only syntax sugar for instanceof, but I'd
still rather have them, than not.
Any why is not possible - this may have been discussed before, not
sure - to throw an exception when the t
> Changing PHP's behavior with a different error level is only a tad bit
> better than adding an INI directive. In general I'd like the core
language
> to behave the same no matter what error level or INI settings.
> I say nuke type-hints and let the purists use instanceof.
>
> Andi
>
Speaking as
On Fri, 28 Mar 2003, Andi Gutmans wrote:
> I guess I'm completely missing your point. Why will PEAR scripts using
> type hints be incompatible with a larger application framework? You
> forget that passing the wrong type to a PEAR function *is* an error.
> How come you suddenly don't want any erro
On Thu, 2003-03-27 at 17:16, Timm Friebe wrote:
> I've implemented an additional feature for type hints that will throw an
> exception instead of bailing out in case an incorrect type is passed.
[...LONG disussion...]
After reading through a bunch of mails this generated, I get the idea
that most
| I don't like E_ERRORS when there is no real reason to bail out.
| As I've already said, non of the other PHP functions trigger E_ERROR
| when the parameters are incorrect; it's just an E_WARNING and a NULL
| value return.
This is a good point. foreach for example issues a warning. So do all th
At 04:56 26/03/2003, Jan Schneider wrote:
Quoting Zeev Suraski <[EMAIL PROTECTED]>:
> That's quite intentional - assignments in ZE2 are handle based, versus
> the
> value based in ZE1. That's more or less the biggest change in ZE2 :)
>
> If you want to create copies like in ZE1 you can use __clon
Since more and more people running into problems with bison,
we should change configure to check for versions 1.28, 1.35
and 1.75. Or does anybody know about any additional version
working or any of the three listed not working?
marcus
--
PHP Internals - PHP Runtime Development Mailing List
To u
Hello,
On 03/28/2003 05:34 AM, Marcus Börger wrote:
I have not had time to look this in detail so I could not reach a
conclusion.
Is the upcoming object model supporting package level member access
retrictions like in Java?
For those that are not aware of what is that, packages are a group of
Hello,
On 03/28/2003 10:57 AM, Andi Gutmans wrote:
We won't support this. (btw it's the default modifier in Java if you
don't write anything else).
I am not defending or suggesting that you support it, I am just asking
if you will. BTW, what is the reasoning for supporting private,
protected an
PHP is not Java - and for good reason. PHP is a rather nice scripting
language. PHP scripts are loaded and run for /each and every /request.
In a sense every request starts with a compile. Clearly to keep the
overhead down you don't want to be compiling in more than is needed to
process the
I had filed a bug report #21855 sometime back.
What the problem was:
When PHP 4.2.3 was being used along with Apache2 (worker model) accessing
the index.php script
of PHPMyAdmin was causing the thread that was servicing the request to die
with this in
the Apache error_log
[notice] child pid
FWIW the version I'm trying to force Edin to use for win32 builds is a
messed-around-with 1.28
(ie that's fine here in the win32 corner ;)
- Original Message -
From: "Marcus Börger" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 28, 2003 8:50 PM
Subject: [PHP-DEV] bison p
Related PRs:
http://bugs.php.net/20120
http://bugs.php.net/22215
According to the first one, 1.50 doesn't seek to work.
PS: last night I mistook what you meant by "test" for test cases :)
Moriyoshi
[EMAIL PROTECTED] (Marcus Börger) wrote:
> Since more and more people running into problems wit
At 10:29 PM 3/28/2003 -0300, Manuel Lemos wrote:
Hello,
On 03/28/2003 10:57 AM, Andi Gutmans wrote:
We won't support this. (btw it's the default modifier in Java if you
don't write anything else).
I am not defending or suggesting that you support it, I am just asking if
you will. BTW, what is th
| The point is that the SOAP (or whatever) library will be interfacing
| with code written by others. If those other people use type hints and
| it blows up with an E_ERROR, we don't have a nice way to handle this
| error and continue serving.
|
| This *is* a disaster, because we are introducing a
At 03:00 PM 3/28/2003 +, Wez Furlong wrote:
On Fri, 28 Mar 2003, Andi Gutmans wrote:
> The point of type-hints is to be able to catch errors in your code
> quickly and not having to write checks, the point isn't to catch
> problems in your code at run-time. And as I said before, if it doesn't
On Fri, 2003-03-28 at 10:52, Andi Gutmans wrote:
> At 03:56 PM 3/28/2003 +0100, Sebastian Bergmann wrote:
> >Andi Gutmans wrote:
> > > OK so maybe we should go ahead and nuke it and save us the argument.
> >
> > Please, no.
>
> The main problem is that people are getting carried away and instead
At 10:57 AM 3/28/2003 -0500, Sterling Hughes wrote:
On Fri, 2003-03-28 at 10:52, Andi Gutmans wrote:
> At 03:56 PM 3/28/2003 +0100, Sebastian Bergmann wrote:
> >Andi Gutmans wrote:
> > > OK so maybe we should go ahead and nuke it and save us the argument.
> >
> > Please, no.
>
> The main problem
42 matches
Mail list logo
