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
Andi Gutmans wrote:
It seems that most people support ?php=. If no one comes up with a
convincing argument against I will add ?php= later on today. BTW, I never
liked the ?= syntax and opposed it at the time but I think today because
many people seem to like it, it makes sense to have ?php=
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
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 be
Is there anybody working on an RTF (rich text format) module?
If not: what requirements would one like for it to have, and for me to
build it?
If so: What's the state.
I'm thinking of a module like the one for PDF. RTF has a few tricky
parts, with respect to whitespace and tag-recognition. I've
