We'll see who reads this, any responses are welcome.
I see a few different issues here:
1) People who want answers for a php-general message post it to the
development forum. This is clearly because they do not understand the
difference, as I doubt anyone wants to waste their own time posting a
Is there any reason we are still supporting PHP3 for error_log?
Specifically that TCP/IP stuff. I was looking at error_log and I was
wondering if anyone had a good objection to me submitting a patch for it
to:
define constants ERRORLOG_SYSLOG, ERRORLOG_EMAIL, ERRORLOG_FILE ..
It's really
I'm playing around with the compiler/executor and I was wondering if
someone could answer a question..
Is there any reasonable way to essentially push/pop the function table?
What I'd like to do is get a function_table hash for only a single file
(pesudo code below):
Look at zend_init_opcodes_handlers() and the zend_opcode_handler array..
John
-Original Message-
From: George Schlossnagle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2003 6:10 PM
To: David Sklar
Cc: Sterling Hughes; [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] Doing something
Such as overriding the opcode handlers for each opcode? I
suppose I could change what the handlers are initialized to in
zend_init_opcodes_handler() so that my new handler does the
serialization and then calls the regular handler. Does that make sense?
Yep
Int
__construct is the new method of defining a constructor, but
the 'bug' you suspect is not a bug. The parser will search
for a function of the same name in the class as the
constructor for backwards compatibility with Older scripts, etc...
But shouldn't __construct() be searched for and used
I was asking myself -- I had assumed that __construct() would be
searched for first. I was /am under the impression __construct() is a
special function that the engine wouldn't allow you to use in PHP5 in
any other context than its intended purpose.
I don't know what Zeev plans on doing with
From HEAD:
./configure works fine (no options)... Make, everything.
But...
./configure --with-apxs=/usr/local/apache/bin/apxs
Causes some weirdness on Make...
[user@localhost]# make
/bin/sh libtool --preserve-dup-deps --mode=compile gcc
-I/home/php/php5/ext/mysql/libmysql -Iext/mysql/
upgrade your libtool to 1.4.3, it is required now.
[user@localhost php5]# ./buildconf
using default Zend directory
buildconf: checking installation...
buildconf: autoconf version 2.13 (ok)
buildconf: automake version 1.4-p5 (ok)
buildconf: libtool version 1.4.3 (ok)
And just to be sure..
Does a snapshot from snaps.php.net compile without running ./buildconf?
Yep it does, actually...
I'll investigate further into it when I get some sleep :)
John
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
$ export SED=sed
$ ./configure ...
Somehow, the variable SED is not set.
I was just looking at the MakeFile trying to figure this out and I was
thinking it must be something like that. It works now -- thanks... But
why would SED suddenly stop being defined? Did I break something
I'll file a bug report on this, but I wasn't sure if it would get
noticed and figured those involved might be interested... As of the CVS
from last Monday (as well as head) ZE2 is segfaulting... Here's the bt..
#0 0x081114b4 in zend_register_functions (scope=0x0,
functions=0x4001a260,
That can be done, but that means 12 commits a day for a
single file. I
dont think that's a good idea.
Is there some way we can harness CVS keyword subsitutuion in a case like
this?
John
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit:
If your using an undocumented parameter, and that undocumented parameter
changes what's the problem? The documentation doesn't say a word about a
mystery undocumented parameter... I don't think we should be too
concerned with someone using something they arguably shouldn't be.
John
I am working on some reader-friendly docs to answer this question, but
for now you can read the ZEND_CHANGES file in the PHP CVS
John
-Original Message-
From: Piotr Sobolewski [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 23, 2003 5:41 AM
To: [EMAIL PROTECTED]
Subject: [PHP-DEV]
The reason I ask is that Shane Caraveo and I were working on the thread
saftey issue, but we couldn't talk about it because we weren't invited
to the PHP5-DEV list
-Original Message-
From: Rasmus Lerdorf [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 23, 2003 5:51 AM
To: Piotr
To answer part of your question:
One more thing: whether this bug is fixed or not, the
documentation must
be clarified! I don't know about you, but I simply don't
understand what
it's supposed to say. Quoting: Note: Also note that foreach operates
What the documentation means is that
Ah, I understand now... This perhaps in a documentation problem then
after all, as there is no way to change this behavior cleanly that I can
see... What about making a copy of the array and all of the references
associated with that array instead of just using the real array?
Just a thought.
This list is for the development _of_ PHP not _with_ PHP, please direct
future questions there
However, I don't understand the question you are asking... If you have
this:
Class A {
function foo() {
echo I am function fooBR;
}
}
Class B extends A {
In order for such a feature to exist the your statement would have to be
(ignoring the ++ operator for now):
$foo = The count is: {$count = $count + 1};
Which means that you'd actually have to evaluate everything inside of {
} as PHP code.. Although the language should be able to accomidate
Is anyone already building Win32 ZE2/PHP executables? I'm planning on
moving all of my development machines over to the ZE2 engine, but I
don't have MSVC handy for my Windows box.
On that note -- Someone before mentioned that we should start building
the source exclusively using ZE2 (for
I tend to agree that completely separating PHP from the modules does
cause a problem when it comes to support modules, etc. However, IMHO I
feel that as the numbers of modules written for PHP increases there
becomes a greater and greater need to separate modules from the core of
PHP.
When it
With 4.3.0 out the door, I just wanted to take a moment and join the
chourus and say Happy new year as well. Peace and happiness to all, and
I'll be sure to throw one back for the success of PHP as well ;)
John
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit:
Perhaps we should try to get documentation for those functions which
don't have anything before we worry about trying to go through and add
more examples for those that do?
John
-Original Message-
From: Tularis [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 31, 2002 5:20 PM
To:
Nah. Can we please put down the swords and start talking about PHP5?
-Original Message-
From: Sascha Schumann [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 29, 2002 12:47 PM
To: Zeev Suraski
Cc: Sebastian Bergmann; [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] Update: Quoting
Can someone enlighten me as to why session_register() and $_SESSION
shouldn't be used togeather? It seems to me the session_register()
function(s) should just be working with $_SESSION anyway... Are they
doing something different? Is this desired behavior if it is doing
something different?
John
Where did you find that recommendation?
http://www.php.net/manual/en/function.session-register.php
Read the note :) I thought it was kind of strange myself... If this is
changed in 4.3 I will update the docs to reflect this, but I wanted to
see what everyone had to say about it first.
John
php_error(E_WARNING, Your script possibly relies on a
session side-effect which existed until PHP 4.2.3. Please be
advised that the session extension does not consider global
variables as a source of data, unless register_globals is
enabled. You can disable this functionality and this
The problem stems from the fact that some users have been
(ab)using session_register when register_globals is off.
session_register is only supposed to be used for the
register_globals=on case.
Those functions need to be updated in the manual then to reflect this
change. If I say
I see that renaming the CGI to php-cgi might break things indeed, and
that's never a good idea. But so is changing the name of the CLI (php)
to something else. It also breaks things, not only for me, but
also for
countless others using the CLI with the name 'php'. We also need to
think about
There is absolutely no reason why you cannot simply include your
functions in your scripts. If you are really lazy, you can even
auto_prepend an include file.
John
-Original Message-
From: Dave [Hawk-Systems] [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 13, 2002 8:56 AM
To:
Esp. when some of us would love to see PHP5 start taking form :)
John
-Original Message-
From: Leon Atkinson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 10, 2002 2:55 PM
To: Edin Kadribasic
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] php.exe - php-cgi.exe
P.S. I wish people
ducking
Maybe phpsh would be a good idea for the name of the CLI? It wouldn't
confuse ppl as much as php-cli
/ducking
Why when I look at phpsh I think Sushi...
John
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Please mention the name change at least in the NEWS file and
maybe php-cli could even output a readable error when beeing
called as cgi.
As I already said, we should put this in the message created at the end
of ./configure, in the release notes, in the news file, on the website,
and perhaps
as a cgi (i.e.
follows one of the many install texts out there).
This is _sorta_ documented but not really, only the
apache2 docs make any mention of it thus far.
Regards,
Philip
On Sun, 8 Dec 2002, Alexander Wagner wrote:
On Sunday 08 December 2002 01:02, John Coggeshall wrote:
I think a big ole
As much as I understand the point of view that renaming the CGI version
of PHP from php(.exe) to php-cgi(.exe) so that we don't have to type
'php-cli' perhaps isn't such a good idea, I am completely against
changing it now. Changing it the first time is obviously causing
problems, changing it
-1, no way...
-Original Message-
From: Jari Vuoksenranta [mailto:[EMAIL PROTECTED]]
Sent: Saturday, December 07, 2002 11:57 AM
To: [EMAIL PROTECTED]
Subject: [PHP-DEV] FR: echo line
I have a feature request: I'd like to have '#' comment like
macro which would expand _ foo to ?
Yes that could happen...maybe we should have another *big*
message for the configure part and a *huge* message in the
release notes and news entries.
This is no different than when register_globals suddenly got turned off.
I think a big ole' message at the end of ./configure will drastically
You can turn it off by setting session.use_trans_sid parameter
to off (btw, it is off by default).
You really should use the session.use_only_cookies directive.
John
Bye,
Ivan
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
);
add_index_long(return_value, 1, result-height);
-Original Message-
From: Derick Rethans [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 05, 2002 1:39 AM
To: John Coggeshall
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: [PHP-DOC] #20822 [Com
The return false part is ok but why not showing the warnings
from fopen?
Well, the issue here is in the bugreport... It's not an issue of PHP
throwing a warning when a file doesn't exist and is attempted to be
opened, but it was throwing the error if the filesize was zero.. I could
see that
For what it's worth, I am in agreement with Derick... Consistency is
important..
Besides... A rose is still a rose, even if it's called
sweet_smelling_flower ;)
OK, I will admit the '_' is then OK, but I rather do not use
it in this case, since I would like to use that for a more
session
+1
-Original Message-
From: Ilia A. [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 04, 2002 3:23 PM
To: Derick Rethans; PHP Developers Mailing List
Subject: Re: [PHP-DEV] New SNMP function names
Consistency is always good and adding aliases for newly added
functions seems
like
I've changed the getimagesize() function so that it RETURN_FALSE on
every error, and disables the error reporting if the file fails to open
(it still returns RETURN_FALSE)
If no one has a problem, I'll commit.
John
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Brad:
I'm going to take a real stab in the dark here and say that you know
Shane Caraveo. I was at PHPCon with him presenting in October and I was
talking about an idea I had to implement opengl in PHP... He said that
someone by the name of Brad (at least, that's what I recall) was working
on a
Yeah I know that shady guy Shane.
Heh. He is shady, isn't he? ;)
Well, it's defintly experimental. There are bindings for
opengl and glut. You can run some sample apps that use the
glut api. Its pretty cool. Me and Marcus were working on off
screen redndering with OSMesa. That would allow
Hey all
I was playing around and I'm running into a problem with a hashtable...
Basically, it's segfaulting my code :) Specifically, I'm trying to
return the number of items in the hash...
if(zend_hash_num_elements(hash) == 0)
Which causes the following:
Program received signal SIGSEGV,
AFAIK, PHP is designed to function on any standard ANSI-compatible C
compiler (as a goal). Unless this has changed, I don't know if opening
the door for C++ development is the best of ideas (IMHO)
John
-Original Message-
From: J Smith [mailto:[EMAIL PROTECTED]]
Sent: Thursday,
is looking
to do it on
either a personal basis or for some proprietary extension, so
it's not like
PHP itself would suddenly become polluted with C++.
J
John Coggeshall wrote:
AFAIK, PHP is designed to function on any standard ANSI-compatible C
compiler (as a goal). Unless this has
This bug was changed to a documentation problem, and I'm a bit confused
as to what exactly the issue is
For($i = 'A'; $i = 'Z' $i++) echo $i;
I'm assuming this *should* echo the A-Z alphabet (which it doesn't)..
But, since it was changed to a documentation problem -- is the current
form
This bug was changed to a documentation problem, and I'm a bit confused
as to what exactly the issue is
For($i = 'A'; $i = 'Z' $i++) echo $i;
I'm assuming this *should* echo the A-Z alphabet (which it doesn't)..
But, since it was changed to a documentation problem -- is the current
form
-
From: Dan Rossi [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 28, 2002 7:06 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [PHP-DEV] RE: Bug #2965
i'd try use chr($i) or something like that and start @ A value
-Original Message-
From: John Coggeshall [mailto:[EMAIL
I'm conflicted on this one. On the one hand you've got PHP
somewhat at fault for treating letters as special characters
(such that 'Z'+1 == 'AA') rather than as their ordinal
equivalents (such that 'Z'+1 == ord('Z')+1 == 91 == ord('[')
== '[' ) which IMO is an ugly thing.
I personally like
67108860 bytes = 64 mb
64M will also work, I believe.
John
Jonathan Williams [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Could someone
please help. Running Linux 7.3 RH with 512 MB Ram with
Apache and PHP 4. I receive the following error and was
Alrighty :)
I'm not going to force-feed localization down anyone's throat myself,
and since there are some who seem almost pissed at the idea... Well :)
Looks like there's just not a need for it.
Anyway... So what of my actual patch we were discussing at some point? I
never got a real answer as
Unless told otherwise, I'm already planning on making a few changes and
committing.
John
-Original Message-
From: Ivan Ristic [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 26, 2002 2:50 PM
To: [EMAIL PROTECTED]
Cc: 'James Aylett'; 'PHP Developers Mailing List'
Subject: [PHP-DEV]
My bad then :) I was under the impression that we had moved passed this
and no one had a real issue with it.
I'll hold off on it then.
John
-Original Message-
From: Sterling Hughes [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 26, 2002 3:18 PM
To: John Coggeshall
Cc: 'Ivan
: Tuesday, November 26, 2002 4:00 PM
To: John Coggeshall
Cc: 'Sterling Hughes'; 'Ivan Ristic'; 'James Aylett'; 'PHP
Developers Mailing List'
Subject: Re: [PHP-DEV] Redirect on Error (not localisation)
John Coggeshall [EMAIL PROTECTED] wrote... :
My bad then :) I was under the impression that we
http://coogle.homeip.net:81/php/patches/error_redirect.txt
John
-Original Message-
From: Derick Rethans [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 26, 2002 4:22 PM
To: John Coggeshall
Cc: 'PHP Developers Mailing List'
Subject: Re: [PHP-DEV] Redirect patch URL
On Tue, 26 Nov
, the assumption
Here is that error_redirect would be set to OFF (hence, standard
Error reporting would apply). That can be confirmed by adding
An additional check to disable error-redirects if it is a CLI
PHP within the code...
Cheers,
John
Regards,
Philip
On Tue, 26 Nov 2002, John Coggeshall
Multi-lingual error codes open's up pandora's box, let's not go
there.
I have to disagree with you here Sterling. Worrying about support for
non-english errors in php-general, etc is a bad, bad excuse not to
implement them. The benefits of a completely constant-based error system
(with
Wow..
Alrighty... I've read through all of this stuff -- everyone seems to
have quite a strong opinion on this one :) Since I kinda brought it up
with Maxim, let me provide a concept of implementation and defend it...
I'd of course love to hear what you guys have to say...
I am completely +1 to
I am definitely -1 for this idea. XML is a buzzword, it is
good in some cases
not so good in others, definitely not a one size fits all
solution. In PHP's
case it would add decency on an XML parser, make life of
developers adding,
modifying, removing error messages difficult and just like
Because errors need to be loaded into memory by some
mechanism, stored in a
hash table? Meaning that during startup I will be penalized
for this process.
Hash table has it own overhead as well meaning that PHP memory
usage will
increase, for a server running 200-300 apache children
I had wanted to avoid this whole thread, but decided to read this one
message, and ouch. While I'm all for internationalization in general,
I'm realy not all for using xml wherever possible just because it can
be. There are existing techniques and libraries designed for
this, find
one and
Nearly any singular operation is fast, the question is what
happens when it is
done often. For a database stored on disk we are talking at
least 2-3 drive
seeks + reading of meta information at the start of the
database. While it
may be negligible for a single process it does add up. Given
Maxim (and anyone else who is interested)
Shall we try to get a patch for this working then? I'm thinking perhaps
starting off with an XML file defining the error messages, which is
converted to a cdb for actual use.
Anyone else game?
John
-Original Message-
From: Sascha Schumann
I've been cut off from my e-mail since Thursday, so I'm going to have to
play catch-up a little here...
Issue #1: Maxim's Error handling suggestions
I completely agree with the concept of language-specific errors. I'll be
happy to implement a system on that. However before we do that I think
[1] The annoying thing is that FATAL errors can't be handled
by an error
handler
With the patch they can be handled without any issues.
I don't like the 500 way either, because you simply loose
the entire
environment
the bug occured in.
You'll lose the entire environment in any
Okay...
Well, even though I've yet to convince Derick and a few others... I did
see enough interest in this to create a patch. This creates two new
directives: error_redirect (bool) which turns this on/off, and
error_redirect_url (string) which is the URL to redirect to upon error.
In order for
Shane (and everyone else):
Why don't we move PHP into a separate executable. Design a
thin ISAPI DLL which purely passes the data which the ISAPI
DLL exposes between the IIS process and the PHP process (or
process-pool for added reliability). The resulting page is
processed in the
: John Coggeshall [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 20, 2002 10:48 PM
To: 'James Cox'
Subject: RE: [PHP-DEV] error handling
that can't really be done because parsing has happened, and so
output has started -- but if we return status 500, the
webserver
efficient.
marcus
At 12:56 21.11.2002, John Coggeshall wrote:
Okay...
Well, even though I've yet to convince Derick and a few
others... I did
see enough interest in this to create a patch. This creates two new
directives: error_redirect (bool) which turns this on/off, and
error_redirect_url
|And how about that we change PHP so that it changes
|the status of the response to 500 on a fatal error? Then
|you would be able to use the Apache directive
|
|ErrorDocument 500 /handle-my-errors.php
|
|to deal with them. You would have to use output buffering,
|of
this into a 500 error to Apache.
John
-- james
-Original Message-
From: John Coggeshall [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 20, 2002 10:48 PM
To: 'James Cox'
Subject: RE: [PHP-DEV] error handling
that can't really be done because parsing has happened, and so
without breaking old code.
Please RFC of course :)
John
-Original Message-
From: Chris Shiflett [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 20, 2002 6:31 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: [PHP-DEV] error handling
--- John Coggeshall [EMAIL PROTECTED
If ErrorDocument is implemented as a sub-request in Apache, it
would be
enough for PHP to set one or more Apache notes with the necessary
information.
Again, what about IIS, etc?
John
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Who cares? :) It really would be much better if some person
who thinks
IIS rulez fixes the ISAPI module. If that doesn't work
correctly nobody
should use it at all.
I'm not saying I'm a IIS fan. :) I rather implement one solution
Which works, period. IMHO that's better than have different
On a sidenote, is it possible in Zend to implmement something such as:
$string = Foobar;
$string = $string[1];
I actually thought that would work, however upon testing it throws an
error... Just curious.
John
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit:
|And this can never be supported safely, as a parse error leaves the
|parse in an unstable state. Also, I really don't think that we should
|try to add hacks to make this possible.
Is this directed toward my wish (of having a secondary error if the
custom error handler also errors) or toward
Both? I'm not totally sure what you mean with when the custom error
handler also has errors. Can you elaborate?
Okay
?php
set_error_handler(myerrorhandler);
function myerrorhandler($errno, $errstr, $errfile, $errline) {
echo There was an error.;
This is what I sent Derick about a possible method of implementing a
custom error handler for E_PARSE, etc... Free to flame if I'm off base
here :)
-Original Message-
From: John Coggeshall [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 18, 2002 3:52 AM
To: 'Derick Rethans'
Subject
Can't argue with that, however (;)), I find it annoying that
PHP stops
processing if there is a parse error passed to an eval()
command. I'd
like a way to make eval() just return E_PARSE if the script
passed to
it fails.
This is exactly the type of situation where E_PARSE really bothers
uhm, John, we dont have a E_PARSE yet.
It's late... I actually stared at that sentence for about 30 seconds
trying to determine if I had spelled PARSE wrong... Then I actually went
and checked the manual to make sure I hadn't lost my mind and there was
actually a E_PARSE constant... Now I'm just
hmm, I really thought we didn't have one, as it doesn't make sense at
all :)
Ha! I'm not crazy! :)
Having a solid way to
gracefully bow-out because my cat managed to open, fill with
junk, and
save a critical include file would just be nice. The choice between
the blank screen, or a nasty
?php header(Location: http://somewhere.com/error.php?errno=4;); ?
This way, users who don't care can still re-direct a browser
to a nice
and pretty sorry, the server is really screwed HTML page... Or, if
they'd like, they can simply take that error number and create a
error-handler in
Did we ever come to some sort of agreement on the error handler thing?
I'd like to maybe look into working on maybe putting together the
redirect-on-error system we discussed (implementing a new directive
which if set will re-direct the user to another web page if PHP errors
out).
Someone
|I know this is possible now, but not within the error handling
|function of PHP, or without setting a custom error handler.
Well, it's not really possible now -- a E_PARSE won't get thrown to a
custom PHP handler, it'll just die with a parse error.
If there is an improvement to be made,
: [PHP-DEV] show_source()
|
|
|I would actually love to see that :)
|
|
|John Coggeshall [EMAIL PROTECTED] wrote in message
|news:000701c28c5e$ac9cb200$9d10fea9;coogle...
|
|If no one has an objection, I'll look into making some of that happen.
|
|John
|
|
||-Original Message-
||From
|I thought we're going with 5.0.0 after 4.3.0? Obviously we'd
|maintain the
|4.3.0 branch and continue to release bug fix releases. Or do
|you think we
|should wait for 4.3.1? I'm a bit concerned about 5.0 lingering for too
|long. You can see how 4.3 has lingered.
I was under the impression
|What is left to do to get 4.3.0 out the door? Anyone have any
|sort of list or idea Of where things need to be polished/cleaned up?
I meant of course beyond the little TODO already posted :)
John
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit:
I haven't received a CVS Daily report in a couple of days... Something
broken?
John
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
The validation for an e-mail address is huge, if you don't believe me
pick up a copy of Mastering Regular Expressions by O'Reilly and look it
up And they can't claim it's perfect...
I don't know about is_alpha() or is_alnum(), IMHO, I think
is_valid_email() just doesn't belong.
John
|syntax:
| var [getter method] [setter method] $variable .;
I think this syntax looks pretty interesting. It would allow the
developer to create get/set if desired and doesn't look too strange
either..
I'd like to see it in action myself :)
John
--
PHP Development Mailing List
What about something like this...
Class foo {
var $myfoo; // Private variable
pubvar $myfoo2; // Public variable
}
Class bar extends foo {
pubvar $mystuff;
}
$a = new foo();
$a-setmyfoo2(5);
echo $a-getmyfoo2();
$b = new bar();
$b-setmyfoo2(10);
makes the assumtion that the user knows how the syntax
|works.. -
|eg. searching the file for getOrange would return nothing...
|
|Regards
|Alan
|
|John Coggeshall wrote:
|
|What about something like this...
|
|Class foo {
|
| var $myfoo; // Private variable
| pubvar $myfoo2
I was just playing with glob() and realized that its pretty undocumented
(no flags doc'd) and none of the constants (GLOB_ONLYDIR for example)
are actually defined in PHP
Just wanted to see if anyone is doing something with this, if not
(unless someone has an objection) I'll get put the
I was digging around the ext/standard today and I wanted to do something
with the file access stuff, however I'm a bit lost on something... I'd
appreciate it if someone could explain this (as it's basically
undocumented).
What is the fourth parameter for the fopen() function? It's listed as a
The only thing I see wrong, is perhaps that Shane and I are working on a
new run-tests script (see run-tests2.php)
Since the script (at least the CLI class) basically works just as well
as the current run-tests.php (as far as I've seen thus far)... Well, I'm
just worried your patch will end
recent discussions
|on php-qa, I doubt that :).
|
|Another option would be, to keep run-tests2.php in there and
|after 4.3.0-release merge the changes?
|
|At 17:39 1-11-2002, John Coggeshall wrote:
|
|
|The only thing I see wrong, is perhaps that Shane and I are
|working on
|a new run-tests
1 - 100 of 104 matches
Mail list logo