I don't have access to the PHP CVS at the moment (note to self: get a C
compiler)... but I wanted to ask how this will affect (or will it?) HTML
generated from within included PHP files. Eg. A is at web root and
includes
B in a subdirectory X. B generates HTML that calls for image C.gif in
I've said it before, but I *really* am convinced now, that we should:
- At least allow $str{index} (while _deprecating_ the array $str[ ] indices)
- _possibly_ also allowing $str{start..end}
- and if the above is allowed, then I think you should also allow
$str{..end} and $str{start..}
But
- Right now this also effects things like opening php.ini. It'll now
always
check in the current working directory for php.ini. I think this
doesn't
screw up todays behavior.
Isn't this a huge security risk? When there is something wrong so that
php.ini can't get read where it
!
To reply, use the web interface found at
http://bugs.php.net/?id=11962edit=1
Jeroen van Wolffelaar
[EMAIL PROTECTED]
http://www.A-Eskwadraat.nl/~jeroen
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Hi,
I've made a patch for 10721, based on justin's, and it now works
correctly.
Andi/Zeev, would you please commit this?
Jeroen
Jeroen van Wolffelaar
[EMAIL PROTECTED]
http://www.A-Eskwadraat.nl/~jeroen
Index: zend_builtin_functions.c
How about having some 'reject' button/link on the bug pages? Just like with
the notes: The sender gets a default mail with: read bugs do and don't,
include sample, ask php-general first, etc. And the bug gets bogusfied
automatically with a default comment if none is supplied.
I think it'd be
, please drop me a line (and of course also
when they don't)
Greetz,
Jeroen
Jeroen van Wolffelaar [EMAIL PROTECTED]
http://www.A-Eskwadraat.nl/~jeroen
Index: math.c
===
RCS file: /repository/php4/ext/standard/math.c,v
retrieving
Has anyone idea's for a good syntax?
I think there are enough classes for mime-mail handling, maybe someone
could get one into PEAR...
Hm, so you don't think it'd be a good think to get in PHP itself? There are
numerous functions that are less common-used, and can be
written very well in
The mail() function can be used to send email with attachments
and special types of content. This is accomplished via MIME-encoding
- for more information, see
http://www.zend.com/zend/spotlight/sendmimeemailpart1.php;
Just a wild idea, but maybe we should add a real
Hi,
I've rewritten the pow(base,exp) function. It is attached.
In stead of a mere call to the c-lib function pow, this one actually does
something more smart. This is to protect those people not knowing that there
is huge difference between raising to an integer power and raising to a
IMPORTANT: I didn't test it yet, I'm not even sure there are no compile
errors.
(My linux machine doesn't have libtool 1.4 :-(( )
Hey, I can now compile :)
And there is an error, so ignore this for now :(
Please use proper Z_* macros, that is Z_LVAL_PP(exp) instead of
Z_LVAL(*exp).
You use *_PP variants for ** pointers, and _P for * pointers.
k.
I've now fixed the compile problems, it will compile now.
Even better: it works :-)
See attachment.
Greetz,
Jeroen
new_pow_func.c
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
And try to use ZEND_NUM_ARGS() wherever possible. Like here:
zend_get_parameters_ex(ZEND_NUM_ARGS(),zbase,zexp);
I'm fairly new to C, and surely new to the php-implementation, so I took
this from many, many other functions, where it was done that way... I
haven't noticed any function
Hi,
I've fixed some bugs in the function, and believe it is now correct. It's
best to come up with a whole bunch of tests, since there are 25 conditional
expressions in it, for 25 different cases... This is due to the nature of
pow(), and the fact it is now overloaded. pow(0,0) is now fixed to
The patch is attached, for line-breaking reasons.
I also noted a probably-wrong if-statement, added a comment about that,
but didn't fix it. Would someone have a look at it.
IMPORTANT: did *not* test the patch, as I doen't have the equip here to
compile.
Greetz,
Jeroen
Jeroen van Wolffelaar
On Sat, 19 May 2001, Hartmut Holzgraefe wrote:
Jani Taskinen wrote:
Do not close any bug reports before the possible bug is REALLY
fixed.
so you claim it has *not* been fixed by the latest updates that kk
made to phpdoc/en/language/oop.xml ??? ;)
I'd almost say: RTFM :-D
Jeroen van
101 - 116 of 116 matches
Mail list logo
