Hi all,
I'm new to the list.
I have modified snmpget and snmpgetnext to accept
mixed type object_id. It can be a string, specifying a single object_id, or an
array of strings specifying multiple object_ids.
The patch is against PHP 5.2.5. Please comment.
Thanks.
--
Best Regards,
Leon
hi!
On Fri, Jan 16, 2009 at 11:23 AM, Leon KUKOVEC leon.kuko...@gmail.com wrote:
Hi all,
I'm new to the list.
Welcome :)
I have modified snmpget and snmpgetnext to accept
mixed type object_id. It can be a string, specifying a single object_id, or an
array of strings specifying multiple
Hi everyone.
I posted this on php.windows a two days ago without a response. Maybe
someone here can help me.
Recently someone using our software told us about problems with
generated filenames being too long. I did some research on the net and
some quick tests on Vista Business, and it
Hello,
I have modified snmpget and snmpgetnext to accept
mixed type object_id. It can be a string, specifying a single object_id, or
an
array of strings specifying multiple object_ids.
The patch is against PHP 5.2.5. Please comment.
The patch is missing, please use a .txt extension.
A
Hi,
I was looking at namespaces in PHP 5.3,
http://de3.php.net/manual/en/language.namespaces.definition.php.
There I found myself wondering why a leading backslash in namespace
declaration
is not allowed. For example:
?php
namespace \A {
echo in namespace \\A\n;
}
?
I image that a
hi,
On Fri, Jan 16, 2009 at 11:42 AM, Karsten Dambekalns kars...@typo3.org wrote:
Recently someone using our software told us about problems with generated
filenames being too long. I did some research on the net and some quick
tests on Vista Business, and it seems there is indeed still a
Hi Pierre.
On 16.01.2009 14:33 Uhr, Pierre Joye wrote:
While NTFS supports path lengths of up to 32k characters,
By the way, this limit is approximative.
In what way?
There is no plan yet to increase this value. The main problem is that
the maximum length of a path is volume dependent,
On Fri, Jan 16, 2009 at 3:53 PM, Karsten Dambekalns kars...@typo3.org wrote:
Hi Pierre.
On 16.01.2009 14:33 Uhr, Pierre Joye wrote:
While NTFS supports path lengths of up to 32k characters,
By the way, this limit is approximative.
In what way?
There is no plan yet to increase this
On Fri, Jan 16, 2009 at 5:03 PM, Pierre Joye pierre@gmail.com wrote:
Well, not really. Our names include some information, so hashing isn't
really an option. For now we'll probably just skip supporting Windows.
The problem is exactly the same on any OS, only the size varies. The
limit is
Hi.
On 16.01.2009 17:12 Uhr, Pierre Joye wrote:
The problem is exactly the same on any OS, only the size varies. The
limit is not higher either. What do you use as naming for your
entries?
Oe example with 229 characters:
Hi,
On Thu, 2009-01-15 at 17:07 -0800, Stanislav Malyshev wrote:
Index: Zend/zend_modules.h
[...]
@@ -70,8 +68,7 @@
struct _zend_module_entry {
unsigned short size;
unsigned int zend_api;
- unsigned char zend_debug;
- unsigned char zts;
+ char *build_id;
hi
On Fri, Jan 16, 2009 at 6:27 PM, Karsten Dambekalns kars...@typo3.org wrote:
Oe example with 229 characters:
Hi!
If I got it right it will, when loading a 5.3 extension in 5.2, try to
read the extension name from the wrong location and therefor most likely
segfault while generating the error message. (it will also try to read
zend_debug and zts, of course, but there it should be able to safely
read
Pierre Joye escribió:
which is defined at
compile time
can also be obtained at runtime using pathconf(3)
--
We have art in order not to die of the truth - Friedrich Nietzsche
Cristian Rodríguez R.
Software Developer
Platform/OpenSUSE - Core Services
SUSE LINUX Products GmbH
Research
Hi,
in every programming language, method calls are expensive. Especially in
PHP, which does not spend any effort during compile time to resolve method
calls their target (and cannot due to the possibility of lazily loading
classes using include w/ variables). I recently did some performance
On Fri, Jan 16, 2009 at 7:08 PM, Cristian Rodríguez crrodrig...@suse.de wrote:
Pierre Joye escribió:
which is defined at
compile time
can also be obtained at runtime using pathconf(3)
Yes, (and GetVolumeInfo on win), but then we have to allocate the path
instead of using static size, in
Hi Timm!
Worth it? I think that's absolute necessity to add this patch, because if it
gives almost 2 times speed boost for typical frameworks, it's just fantastic
(well, the less calls, the less performance boost, but really some monsters
like Zend or CakePHP and others will definitely benefit
Hi!
Attached is the patch implementing build ID. Please comment. If no
objections are raised I'm going to commit it tomorrow.
...
+ fprintf(stderr, Cannot load %s - it was build with configuration %s,
whereas running engine is %s\n,
Why not to call zend_error instead?
It would make more
Hi,
Ok, my proposal to drop OO support from Closures was exactly embraced.
All I want you guys to think about is how you want to deal with this
in terms of the PHP 5.3 release. If no decision is found and
implemented over the weekend, this topic will essentially cement the
need for an
19 matches
Mail list logo
