I haven't been following this too closely, and I'm not exactly sure what I'm
looking for, but I used Mozilla 1.5 and all seemed to look alright (except for
a blank line at the top and bottom of the preformatted text).
Gordon Hemsley
Lisa,
With my testing, \n causes a double line break in Netscape Mail
and Internet Explorer 6 on windows. However, using \n inside
instead of works in both browsers. For my test, I took the page
at http://pear.php.net/manual/en/core.pear.pear.seterrorhandling.php and
replaced the with \n.
It's the fastcgi stuff that is incompatible with win95 - everything else
should still work.
The c-client library includes some funky s-channel stuff that might not work
under win95 or NT if you don't have a particular version of IE or a service
pack installed - I don't know the precise details off
I got 4.3.3 to work on win95 ok... (support of 95 is kind of essential
for php-gtk) as _alot_ of offices are still using it.. - If all the user
does is type up letters+print documents, where's the cost/benefit in
upgrading.. :)
Regards
Alan
Edin Kadribasic wrote:
On Wed, 29 Oct 2003, Andi Gutm
Fixed, was a ZTS problem. But there are a LOT of warnings during compile
with non-gcc compilers.
At 01:56 30.10.2003, Uwe Schindler wrote:
After updating the mbstring extension by hirokawa in RC3 it is broken and
does not compile:
System: Solaris 9 SPARC
Compiler: Forte7
RC2 worked perfect.
/b
Frank M. Kromann wrote:
hmm. I'm using php 4.3.3-dev with imap on Windows 2000 server and XP Pro.
That works fine for me.
NT = NT 4.0. Right?
What changed since 4.2 that broke compatibility? Would it be easy to add
it back? Or is 4.0 too old to maintain it? If it's trivial...
Oliver
--
GB/E/IT d
>
> PHP doesn't work on Windows 95 as of 4.3.0, and NT support is becoming
> incomplete (ext/imap for example does not work on NT).
>
hmm. I'm using php 4.3.3-dev with imap on Windows 2000 server and XP Pro.
That works fine for me.
- Frank
--
PHP Internals - PHP Runtime Development Mailing Li
On Wednesday, October 29, 2003, at 05:49 PM, [EMAIL PROTECTED]
wrote:
It seems that PHP 5 treats all methods as lower case, so that text()
is Text(). Is this going to remain this way?
Yes. It's the PHP Way (tm).
George
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, v
It seems that PHP 5 treats all methods as lower case, so that text() is
Text(). Is this going to remain this way?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Wed, 29 Oct 2003, Andi Gutmans wrote:
> Argh, this only works on Windows 2000 and later or Windows 98 and later.
> I guess I'll need to #ifdef it somehow. Anyway, I'd still like you to check
> it as I assume you're not using Windows 95 or NT 4 :)
PHP doesn't work on Windows 95 as of 4.3.0, an
Argh, this only works on Windows 2000 and later or Windows 98 and later.
I guess I'll need to #ifdef it somehow. Anyway, I'd still like you to check
it as I assume you're not using Windows 95 or NT 4 :)
Andi
At 11:31 PM 10/29/2003 +0200, Andi Gutmans wrote:
Okay, it should work now. Please check
Okay, it should work now. Please check and let me know.
Andi
At 11:17 PM 10/29/2003 +0200, Andi Gutmans wrote:
Forget it. I screwed up. It doesn't work yet.
At 11:12 PM 10/29/2003 +0200, Andi Gutmans wrote:
Hey,
I might have fixed this. Can you please check the latest CVS and let me
know if it
Forget it. I screwed up. It doesn't work yet.
At 11:12 PM 10/29/2003 +0200, Andi Gutmans wrote:
Hey,
I might have fixed this. Can you please check the latest CVS and let me
know if it works for you?
Thanks,
Andi
At 03:36 PM 10/29/2003 +, Pete Dishman wrote:
Hi,
The fact that require_once
Hey,
I might have fixed this. Can you please check the latest CVS and let me
know if it works for you?
Thanks,
Andi
At 03:36 PM 10/29/2003 +, Pete Dishman wrote:
Hi,
The fact that require_once()/include_once() are case-sensitive on Windows
was reported in bug 18630 http://bugs.php.net/bug
At 12:16 PM 10/29/2003 -0500, Adam Trachtenberg wrote:
On Wednesday, October 29, 2003, at 11:39 AM, Andi Gutmans wrote:
Is it case-preserving like Windows? Does realpath work on MAC OS X and
give the case preserved name?
I don't have easy access to a Windows machine to test, but I think the
answ
After a little discussion on php-general[1], I wrote a patch that basically
allows two new php.ini entries: highlight.prepend and highlight.append. They
default to what the output currently is ('' and
'')
The code effects four files; ext/standard/basic_functions.c, main/main.c,
Zend/zend_highl
On Wednesday, October 29, 2003, at 11:39 AM, Andi Gutmans wrote:
Is it case-preserving like Windows? Does realpath work on MAC OS X and
give the case preserved name?
I don't have easy access to a Windows machine to test, but I think the
answer is yes:
[EMAIL PROTECTED]:~/Documents/php/test] $ l
At 11:35 AM 10/29/2003 -0500, Adam Maccabee Trachtenberg wrote:
On Wed, 29 Oct 2003, Andi Gutmans wrote:
> No I was not thinking about lower casing (although that is an option). I
> was wondering if it's possible to do something like realpath() in Windows
> which gives you the pretty name (the cas
would it not make sense to implement
a) export the ioctl defines DIO_TIOCMGET etc.
b) write a generic dio_ioctl($fh,$type,$args) function, with switch/case
on the $type
that way implementing more features for ioctl would just be a matter of
adding the define and handling any special args/return
On Wed, 29 Oct 2003, Andi Gutmans wrote:
> No I was not thinking about lower casing (although that is an option). I
> was wondering if it's possible to do something like realpath() in Windows
> which gives you the pretty name (the case preserving name). We could then
> use that and it would look g
At 05:15 PM 10/29/2003 +0100, Derick Rethans wrote:
On Wed, 29 Oct 2003, Andi Gutmans wrote:
> At 04:02 PM 10/29/2003 +, Peter Dishman wrote:
> > > How is this a BUG? It's just a feature on windows where you have
> > > case-insensitive filenames. I fyou want to handle that, just use one
> > >
Added two functions:
dio_modemget(resource fd) - returns the control line status of a serial port
dio_read_waiting(resource fd) - returns the number of bytes waiting in
the input buffer
(note: i have submitted a patch for dio_modemget before, but since
current CVS doesn't have it, I'm sending i
Wojtek Meler <[EMAIL PROTECTED]> wrote:
> Moriyoshi Koizumi wrote:
>
> >Hi,
> >
> >First, maybe you want to see bug #22836 (http://bugs.php.net/22836), that appears
> >to describe the very problem you have.
> >
> Probably yes. I assume that it won't be fixed in ZE1, will it?
> Is there any way t
On Wed, 29 Oct 2003, Andi Gutmans wrote:
> At 04:02 PM 10/29/2003 +, Peter Dishman wrote:
> > > How is this a BUG? It's just a feature on windows where you have
> > > case-insensitive filenames. I fyou want to handle that, just use one
> > > style in your code (ie, always lower case).
> >
> >I
* Thus wrote Lisa Seelye ([EMAIL PROTECTED]):
> Attached is a patch to change the behavior of source highlighting
> functions to use instead of .
> This patch also introduces \n and \t when the parser encounters one
> (this change is mainly for readability).
Slight problem with:
zend_printf("\
At 04:02 PM 10/29/2003 +, Peter Dishman wrote:
> How is this a BUG? It's just a feature on windows where you have
> case-insensitive filenames. I fyou want to handle that, just use one
> style in your code (ie, always lower case).
I take it then this is unlikely to change in the future? Fair en
> How is this a BUG? It's just a feature on windows where you have
> case-insensitive filenames. I fyou want to handle that, just use one
> style in your code (ie, always lower case).
I take it then this is unlikely to change in the future? Fair enough I
suppose.
However if I create a patch/dif
On Wed, 29 Oct 2003, Pete Dishman wrote:
> Hi,
>
> The fact that require_once()/include_once() are case-sensitive on Windows
> was reported in bug 18630 http://bugs.php.net/bug.php?id=18630 , however the
> bug was then just closed as a documentation problem and nothing was changed,
> which is why
Hi,
The fact that require_once()/include_once() are case-sensitive on Windows
was reported in bug 18630 http://bugs.php.net/bug.php?id=18630 , however the
bug was then just closed as a documentation problem and nothing was changed,
which is why I'm sending this here rather than adding to the bug r
As promised, I'm rolling up beta 2 tomorrow morning. I know Marcus
submitted the last patches he wanted to get in and so did I.
People who haven't updated ZEND_CHANGES or NEWS are welcome to do so.
Thanks,
Andi
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://
Moriyoshi Koizumi wrote:
Hi,
First, maybe you want to see bug #22836 (http://bugs.php.net/22836), that appears to describe the very problem you have.
Probably yes. I assume that it won't be fixed in ZE1, will it?
Is there any way to fix it for own risk? I saw something in
zend_execute.c with co
Hi,
First, maybe you want to see bug #22836 (http://bugs.php.net/22836), that appears to
describe the very problem you have.
Secondly, you can use various custom gdb macros like printzv, printzn
which are defined in .gdbinit on top of the php source tree.
Moriyoshi
Wojtek Meler <[EMAIL PROTEC
Are there any tools for debugging ZE? I've got a problem with huge script that
at some point behave like all variables were reference to single variable.
I suspect that there is something wrong with EG(uninitialized_zval).
Any hints how to fight it?
I've compiled it with ZEND_INTENSIVE_DEBUGGING a
On 10/28/03 22:34:04, Tal Peer wrote:
On Tue, 28 Oct 2003, Gareth Ardron wrote:
> I can't figure out if this is desired or not, if it's not, I'll
happily
> draft up a patch to alter the behaviour - I just want to make sure
> before I do.
Why should header() start parsing its argument? its only job
On Wed, 29 Oct 2003, Sascha Schumann wrote:
> > Actually, & is the way you need to write it if you are going to be
> > perfectly standards-compliant.
>
> That is correct for URLs in HTML. It is incorrect for HTTP headers
> (there is no entity decoding involved).
True, I should read inste
On Tue, 28 Oct 2003, Rasmus Lerdorf wrote:
> On Wed, 29 Oct 2003, Christian Schneider wrote:
>
> > Gareth Ardron wrote:
> > > $var = "foo=1&bar=2";
> >
> > To clarify:
> > You should use $var = "foo=1&bar=2"; and then $var for header() but
> > htmlspecialchar($var) for your href:
> > - HTTP-Header
36 matches
Mail list logo
