On Wed, 9 Oct 2002, Yasuo Ohgaki wrote:
Colin Viebrock wrote:
This is getting a little more complicated than I think is necessary.
There are two issues here, I think:
a) Fonts. Some people didn't like Arial, so I reverted to letter the
browser decide. Some people didn't like that,
On 8 Oct 2002, Tim Daly, Jr. wrote:
Brad LaFountain [EMAIL PROTECTED] writes:
What engine are you working with 1 or 2?
-brad
I imagine PHP3 == engine 1, and PHP4 == engine 2?
PHP 3 is engine 0.5, PHP 4 is engine 1 and PHP 5 will be engine 2 :)
So you're most likely using engine 1.
I thought that I'd try this out with HEAD, but I found that PHP would
go into an infinite loop. I didn't have time to debug it, so I reverted
to using a regular path instead. Could a session guru take a look and
double check this?
session.save_path=2;/var/tmp-- infinite loop
On 10/09/02, Yasuo Ohgaki [EMAIL PROTECTED] wrote:
AFAIK, there is no Arial that includes CJK.
Arial Unicode MS (that 22MB TTF you'll find in \windows\fonts) seems
to do a good job of including virtually all characters known to man.
BTW: Colin - there is a bug report about phpinfo() - you are
On Wed, 9 Oct 2002, Wez Furlong wrote:
I thought that I'd try this out with HEAD, but I found that PHP would
go into an infinite loop. I didn't have time to debug it, so I reverted
to using a regular path instead. Could a session guru take a look and
double check this?
At 08:34 9-10-2002, Derick Rethans wrote:
For once I agree with yasuo here :) phpinfo() doesn't need to look
pretty, it's for _debug_ output.
Which means it needs to be as clear as possible. Formatting it for readibility
is a plus - you don't want output that's hard to read, as you're already
At 06:02 9-10-2002, Sascha Schumann wrote:
Good point - but also raises, whether to look for this struct in the first
place.
Why not skip it all, and define it ISO C compliant, in php_ namespace?
That would be a possibility, although you never know how
engineers at some random
Before we branch, I would be grateful if someone could verify that we
are detecting fopencookie correctly.
It seems that older glibcs use an off_t parameter for the seeker
function, while newer versions pass an fpos_t * instead.
I've (previously) expanded the PHP_FOPENCOOKIE test in
Wez Furlong wrote:
On 10/09/02, Yasuo Ohgaki [EMAIL PROTECTED] wrote:
AFAIK, there is no Arial that includes CJK.
Arial Unicode MS (that 22MB TTF you'll find in \windows\fonts) seems
to do a good job of including virtually all characters known to man.
Hmm...
I don't have it under my
Doh!
I somehow misread that line, despite reading it several times.
I think it would be useful to emit a warning in this situation.
(if I misread it, I'm sure others will do so also).
--Wez.
On 10/09/02, Sascha Schumann [EMAIL PROTECTED] wrote:
On Wed, 9 Oct 2002, Wez Furlong wrote:
Hi NG.
I'm having problems creating files at a certain location.
If I attemt to create a file it gets created in the rootdir (htdocs) even
though I add a path infront of the file name. I've tried severel ways of
adding a path (with / and \\) but nothing works.
eksample: /nef/articles/54.txt
Hi,
cygwin 1.3.12 (everything upgraded yesterday):
CYGWIN_NT-5.0 WEBMASTER 1.3.12(0.54/3/2) 2002-07-06 02:16 i686 unknown
Small patch needed, for the bundled expat. Otherwise, __imp_ is prepended,
to the symbols and linking fails.
Objections?
Index: ext/xml/expat/expat.h
A new CODING_STANDARDS patch is attached, based on feedback from Andi
and Dan (thanks!). Please review and comment.
--
Jon Parise ([EMAIL PROTECTED]) :: The PHP Project (http://www.php.net/)
Index: CODING_STANDARDS
===
RCS file:
On Wed, Oct 09, 2002 at 09:47:10AM -0400, Jon Parise wrote :
+[11] Prefer emalloc(), efree(), estrdup(), etc. to their standard C library
+ counterparts. These functions implement an internal safety-net
+ mechanism that ensures the deallocation of any unfreed memory at the
+ end
On Wed, 9 Oct 2002, Roman Neuhauser wrote:
# [EMAIL PROTECTED] / 2002-10-09 15:12:57 +0200:
Ah, great. Only 4 failed test left :)
looks like 4.3 will be the best release test harness-wise.
For that to happen we need MUCH more tests. It would be a very nice
thing if there would be a
Le Mercredi 9 Octobre 2002 16:01, Markus Fischer a écrit :
On Wed, Oct 09, 2002 at 09:47:10AM -0400, Jon Parise wrote :
+[11] Prefer emalloc(), efree(), estrdup(), etc. to their standard C
library + counterparts. These functions implement an internal
safety-net + mechanism that
Ok,
I don't think default_properties is what you are looking for.
default_properties store the information about defined variables and their
default value. Like this:
class MyClass {
var $test = mytest;
}
at compile time MyClass class_entry will have test = mytest in its default
properties.
Hello PHP contributors,
I am conducting a survey about the way bugs are handled in open source
software projects. The survey includes questions that can be answered by
developers,testers, bug fixers, project managers, and owners of defect
databases. It is only and only for research purposes and
Hi,
On Wed, Oct 09, 2002 at 09:38:46AM -0500, Gunes Koru wrote:
Hello PHP contributors,
didn't we agree not to do that again?
Jan
--
Q: Thank Jan? A: http://geschenke.an.dasmoped.net/
Got an old and spare laptop? Please send me a mail.
Key7BCC EB86 8313 DDA9 25DF
Brad LaFountain [EMAIL PROTECTED] writes:
Ok,
I don't think default_properties is what you are looking for.
default_properties store the information about defined variables and their
default value. Like this:
class MyClass {
var $test = mytest;
}
at compile time MyClass class_entry
Can you please stop spamming this list?
Derick
On Wed, 9 Oct 2002, Gunes Koru wrote:
Hello PHP contributors,
I am conducting a survey about the way bugs are handled in open source
software projects. The survey includes questions that can be answered by
developers,testers, bug fixers,
Jan Lehnardt wrote:
Hi,
On Wed, Oct 09, 2002 at 09:38:46AM -0500, Gunes Koru wrote:
Hello PHP contributors,
didn't we agree not to do that again?
Well he did shorten his signature - so we are getting somewhere - slowly :)
Jan
--
PHP Development Mailing List
Sascha, could we revisit these session changes? I stuck current head on a
server that runs all sorts of PHP code written by a bunch of different
people. These warnings were everywhere:
Warning: Your script possibly relies on a session side-effect which
existed until PHP 4.2.3. Please be
these are still being sent to [EMAIL PROTECTED]
(perhaps the mail configuration needs to get updated?)
jim
On Wed, Oct 09, 2002 at 03:06:27AM +0200, Charlie Root wrote:
Removing stale files from /var/preserve:
Cleaning out old system announcements:
Removing stale files from /var/rwho:
I have a variable in a smarty template: $product.url ...
Within the smarty template I have: {include file=getTable.tpl} ...
In the included template I have a function called: getTable($url) ...
From the original template where the $product.url resides, I would like to
pass that value into the
I'd like to do a collective rethink of this. The simple description of
the session_register() function in the manual is:
This description was correct initially (I wrote it), but has
not been updated as the session module was extended. I've
noticed this documentation issue in the
FWIW, I didn't manage to understand what the problem was with the codebase
before the patch. Sascha - can you explain it?
I tend to agree with Rasmus about this change being a not-so-good idea, but
maybe we're just not aware of the problems that existed before the patch.
Zeev
At 19:09
Looks good!
Andi
At 09:47 AM 10/9/2002 -0400, Jon Parise wrote:
A new CODING_STANDARDS patch is attached, based on feedback from Andi
and Dan (thanks!). Please review and comment.
--
Jon Parise ([EMAIL PROTECTED]) :: The PHP Project (http://www.php.net/)
--
PHP Development Mailing List
Hey,
If the fopen() fails why not create the directory? It shouldn't be too hard
to do and it'd really improve usability.
Andi
At 09:03 AM 10/9/2002 +, Sascha Schumann wrote:
sas Wed Oct 9 05:03:04 2002 EDT
Modified files:
/php4 php.ini-dist
Log:
On Wed, 9 Oct 2002, Sascha Schumann wrote:
I'd like to do a collective rethink of this. The simple description of
the session_register() function in the manual is:
This description was correct initially (I wrote it), but has
not been updated as the session module was extended.
Unless we're missing some problem I agree with Rasmus here.
I don't see much advantage in changing this.
Of course, there might be a reason
Andi
At 10:40 AM 10/9/2002 -0700, Rasmus Lerdorf wrote:
On Wed, 9 Oct 2002, Sascha Schumann wrote:
I'd like to do a collective rethink of this. The
At 10:40 09/10/2002 -0700, you wrote:
I am not talking about just mine. I am talking about a sizeable subset of
all PHP apps that use sessions. My problem here is that I do not
understand the reasoning for not continuing to allow session_register to
work on global variables regardless of the
On Wed, 9 Oct 2002, Gareth Ardron wrote:
At 10:40 09/10/2002 -0700, you wrote:
I am not talking about just mine. I am talking about a sizeable subset of
all PHP apps that use sessions. My problem here is that I do not
understand the reasoning for not continuing to allow session_register
At 10:47 PM 10/9/2002 +0200, Sterling Hughes wrote:
On Wed, 2002-10-09 at 22:45, Derick Rethans wrote:
On 9 Oct 2002, Sterling Hughes wrote:
On Wed, 2002-10-09 at 22:21, Thies C. Arntzen wrote:
On Wed, Oct 09, 2002 at 06:29:45PM -, Sterling Hughes wrote:
sterling
On Thu, Sep 26, 2002 at 02:10:04AM +0100, Wez Furlong wrote:
All:
I've just committed a php-style version of the ucdata package that Stig
directed me to.
Great!
Stig:
Rather than generate binary data files at configure time, based on
a bundled UnicodeData.txt file which is quite large,
At 11:03 PM 10/9/2002 +0200, Sterling Hughes wrote:
On Wed, 2002-10-09 at 22:56, Derick Rethans wrote:
On Wed, 9 Oct 2002, Andi Gutmans wrote:
At 10:35 PM 10/9/2002 +0200, Sterling Hughes wrote:
On Wed, 2002-10-09 at 22:21, Thies C. Arntzen wrote:
On Wed, Oct 09, 2002 at 06:29:45PM
36 matches
Mail list logo
