Alright.
On 6 Nov 2003, at 2:58 AM, Andi Gutmans wrote:
At 08:01 PM 11/5/2003 -0500, [EMAIL PROTECTED] wrote:
I noticed that echo $object statements in PHP 5 display object ids
that are kept by the engine, so this data is already in the string
form and it is data that exists. As for as a use fo
Jani Taskinen <[EMAIL PROTECTED]> wrote:
>
> Shouldn't you MFH this now?
> (not sure if it was done already :)
> If you do MFH, don't forget to move the BFN from HEAD NEWS
> to PHP_4_3 NEWS..
Well, I tried doing so, but I didn't because the patch would be too huge
for a simple f
Arjen de Rijke wrote:
Hello,
Can anybody tell me why multiple resultsets are not (yet) supported by
the mysqli extension in the php 5.0.0 source? Is it just a matter of
time before the mysql_more_results and mysql_next_result are available
or is there a more serious problem?
Arjen de Rijke
H
Maybe something like that could help you:
#define HAS_INT64_PRIMITIVE
#ifdef MSVC
#define int64_t __int64
#elif ...
#else
typedef struct int64_t_ { int32_t a, b; } int64_t;
#undef HAS_INT64_PRIMITIVE
#endif
- Michael
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: h
On 11/6/03 7:59 PM, Shane Caraveo wrote:
I wonder if there is some way to transform the w3c dom documentation.
That would be a quick-n-dirty way to get the documentation for the dom
extension into php.net docs. Then it could be updated to be more
php-ish, and examples could be pulled from the
Hello,
Can anybody tell me why multiple resultsets are not (yet) supported by
the mysqli extension in the php 5.0.0 source? Is it just a matter of
time before the mysql_more_results and mysql_next_result are available
or is there a more serious problem?
Arjen de Rijke
--
PHP Internals - PHP R
I wonder if there is some way to transform the w3c dom documentation.
That would be a quick-n-dirty way to get the documentation for the dom
extension into php.net docs. Then it could be updated to be more
php-ish, and examples could be pulled from the various talk slides.
Shane
Andi Gutmans w
As one of PHP 5's main improvements is XML how about making a small section
on php.net dedicated to it?
I mean the manual is of course a must but I think it'd be nice to give it
some more exposure.
Maybe a first step would to be slides and stuff you guys wrote up there?
Andi
At 10:06 AM 11/6/20
I've also done a touch of slides on it, as has Sterling, and maybe even
someone else, at talks.php.net. Nothing terribly in-depth.
Shane
Christian Stocker wrote:
My slides from my talk about XML in PHP5 are here:
http://slides.bitflux.ch/phpconf2003/
examples are here
http://slides.bitflux.c
to maintain a good documentation about PHP
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Eric,
Appologies, I should have been more careful to check I actually knew what I
was talking about before I opened my mouth ;-) Didn't realise the existing
private key version came in two separate functions like this. As I said, I'm
a big fan of consistency, but I guess we have two precedents her
Hi !
Richard,
I understand very well the benefit of using only one function to do the
same work, but they are already 2 function that does the same for private
keys and for consistency i think i had to submit 2 function to do the same
job for public keys.
Of course the best way is to have only
On Thu, 2003-11-06 at 13:04, Andi Gutmans wrote:
> At 09:58 AM 11/6/2003 +0100, Stig S. Bakken wrote:
> >Let's sum up the pros and cons:
> >
> >Pros: sexiness?
> >
> >Cons: another BC issue, syntax obfuscation, potential grammar conflicts
>
> Just to be more accurate there are no BC issues and as
On Thu, 6 Nov 2003, Andi Gutmans wrote:
> Sascha,
>
> I don't think it's a private matter.
If there was anything constructive in that long thread of "I
like it" -- "no, I don't!" I might agree with you, but given
the current contents, the noise exceeds the useful debate by
far.
Sascha,
I don't think it's a private matter. Feel free to delete the emails with
this subject when they come in.
Andi
At 01:30 PM 11/6/2003 +0100, Sascha Schumann wrote:
Please move this thread to private email.
- Sascha
--
PHP Internals - PHP Runtime Development Mailing List
To unsub
Please move this thread to private email.
- Sascha
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 05 November 2003 18:39, Andrei Zmievski wrote:
> On Wed, 05 Nov 2003, Ford, Mike [LSS] wrote:
> >
> > I don't think the number of characters is the main issue here --
> > it's about having a *nicer* set of characters. Personally, I'd be
> > still be in favour (although not quite
On 05 November 2003 17:19, Marco Tabini wrote:
> Ford, Mike [LSS] wrote:
> > On 05 November 2003 17:06, Marco Tabini contributed these pearls of
> > wisdom:
> >
> >
> > > Christian Schneider wrote:
> > >
> > > > Marco Tabini wrote:
> > > >
> > > >
> > > > > $a = [[1,2,3],[1=>[1,3,2,2], "a"=>
Mike Robinson wrote:
Perlish or not could not be a real reason for adding or not
adding a feature in PHP. The important thing here is if it
fits to the language concept or not.
Indeed, and IMHO it does, much like
($a==$b)?...
fits in quite well as an alternative to
if ($a==$b)...
It is an a
At 09:58 AM 11/6/2003 +0100, Stig S. Bakken wrote:
Let's sum up the pros and cons:
Pros: sexiness?
Cons: another BC issue, syntax obfuscation, potential grammar conflicts
Just to be more accurate there are no BC issues and as far as I know, there
aren't any grammar conflicts.
Andi
--
PHP Inter
Kouber Saparev wrote:
> Perlish or not could not be a real reason for adding or not
> adding a feature in PHP. The important thing here is if it
> fits to the language concept or not.
Indeed, and IMHO it does, much like
($a==$b)?...
fits in quite well as an alternative to
if ($a==$b)...
It i
My slides from my talk about XML in PHP5 are here:
http://slides.bitflux.ch/phpconf2003/
examples are here
http://slides.bitflux.ch/phpconf2003/examples/
And Sebastian's slides (in german) are here:
http://www.sebastian-bergmann.de/blog/
maybe that helps for a start in really documentating it
Perlish or not could not be a real reason for adding or not adding a feature
in PHP. The important thing here is if it fits to the language concept or
not.
Kouber
"Sara Golemon" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> FWIW- (And I understand I'm late chiming in on this threa
On Wed, 2003-11-05 at 17:48, Andi Gutmans wrote:
> At 11:48 AM 11/5/2003 -0500, Ilia Alshanetsky wrote:
> >On November 5, 2003 11:21 am, you wrote:
> > > Well, like I said before, I am not sure this is a clear case of that. I'm
> > > probably the biggest defender around of the no-magic rule, but [
This one time, at band camp, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> Hey,
>
> Is there any place the updated SimpleXML, DOM, XSL extensions are
> documented? I don't think they are in the PHP manual. This is crucial to
> get the word out because I've gotten quite a few queries from people who
Hey,
Is there any place the updated SimpleXML, DOM, XSL extensions are
documented? I don't think they are in the PHP manual. This is crucial to
get the word out because I've gotten quite a few queries from people who
don't know about the new XML features.
Andi
--
PHP Internals - PHP Runtime
At 02:07 AM 11/6/2003 +0100, Christian Schneider wrote:
George Schlossnagle wrote:
George (thinking [] is pretty but disliking alternative syntaxes)
Ok, let me recap my short visit on this mailing list:
1) Dangling commas in function calls were considered bloat
No, not bloat. I was worried that the
At 08:01 PM 11/5/2003 -0500, [EMAIL PROTECTED] wrote:
I noticed that echo $object statements in PHP 5 display object ids that
are kept by the engine, so this data is already in the string form and it
is data that exists. As for as a use for this feature, one can't easily
say there is not a use;
28 matches
Mail list logo
