good example, because actually I havent
really thought thoroughly whether this can really lead to ambiguity.
I just want to raise this issue, because I think this could be the
hardest part in implementing the feature.
Regards,
--
Jimmy
They asked me "upgrade the NT server", so I installed UNIX
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
.
2. If users can specify the type of a variable, then PHP's WDDX can support
all type which is defined in WDDX standard.
For example binary type. Currently there's no way to create a
WDDX packet with binary type, because PHP don't have binary type
variable. T
ID: 15025
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Scripting Engine problem
Operating System: FreeBSD, Linux
PHP Version: 4.1.1
New Comment:
$c should not have been affected by the assignment to $b because $c
should only be a copy to $a.
What hap
From: [EMAIL PROTECTED]
Operating system: FreeBSD, Linux
PHP version: 4.1.1
PHP Bug Type: Scripting Engine problem
Bug description: Copy of array is affected by reference
You can guess / see from this simple script:
$a = array(5);
$b =& $a[0];
$c = $a;
echo $c[0];
$b
Zeev Suraski wrote:
>
> Generally, a perfect C implementation will always be quicker than a PHP
> implementation, because the scripting engine has its overhead.
It's my impression that an average PHP script will run faster on a
heavily loaded apache server than a compiled executable will get loa
Andi Gutmans wrote:
> It seems that most people support convincing argument against I will add liked the many people seem to like it, it makes sense to have sake.
Let's put it this way: who cares. It doesn't break any existing code,
does it? As long as nobody is *obliged* to use it...
Howeve
Manuel Lemos wrote:
>
>
> I have complete RTF parser and writer code written in C that I am
> willing to donate if anybody is willing to turn it into a PHP module.
It's time we generate a platform somewhere.
> BTW, if you just give a RTF document module the .doc extension, Word
> will still b
Markus Fischer wrote:
>
> Your module is only capable of producing RTF right? Not parsing
> it?
Yes, well... depends how you interpret the word 'parsing'. If parsing is
interpreted in the programmers-sense, i.e. building a parse-tree of any
kind: no. I'm not interested in doing a sort of RTF-vie
files from PHP with dynamic
content, ready to be imported in any RTF-capable wordprocessor (header
mimetype text/rtf) RTF is the most widely understood alternative, and as
it is fully ASCII based, will not be to 'version incompatibility' prone
as the native M$Word formats.
Ideas and sugges
