Professional Web Applications Themes

[PHP-DEV] BUG #18630 - PHP Development

Hi, The fact that require_once()/include_once() are case-sensitive on Windows was reported in bug 18630 [url]http://bugs.php.net/bug.php?id=18630[/url] , however the bug was then just closed as a doentation problem and nothing was changed, which is why I'm sending this here rather than adding to the bug report. Anyway, on systems with case-insensitive file systems this problem effectively makes require_once() useless and means you have to rely on code blocks such as: if (defined("ASRD_INCLUDED")) return; define("ASRD_INCLUDED", TRUE); at the top of every single include file, this is definitely ugly and would be much better replaced by require_once(). Also using this to prevent multiple ...

  1. #1

    Default [PHP-DEV] BUG #18630

    Hi,

    The fact that require_once()/include_once() are case-sensitive on Windows
    was reported in bug 18630 [url]http://bugs.php.net/bug.php?id=18630[/url] , however the
    bug was then just closed as a doentation problem and nothing was changed,
    which is why I'm sending this here rather than adding to the bug report.

    Anyway, on systems with case-insensitive file systems this problem
    effectively makes require_once() useless and means you have to rely on code
    blocks such as:
    if (defined("ASRD_INCLUDED"))
    return;
    define("ASRD_INCLUDED", TRUE);

    at the top of every single include file, this is definitely ugly and would
    be much better replaced by require_once().
    Also using this to prevent multiple inclusions still means that the file
    will be pd multiple times which is an unnecessary performance drain.

    From what I can tell of the code in zend_execute.c, fixing this bug is just
    a matter of taking a copy of the filename and making it lowercase on windows
    systems before adding it to the EG(included_files) hashtable.

    Is there any chance this could be fixed before 4.3.4 is released, as it is
    definitely a bug and not a doentation problem.


    Cheers,
    Pete Dishman

    ------------------------------------------------

    Peter Dishman

    Software Engineer

    Email: [email]peterdtelephonetics.co.uk[/email]

    Address: Telephonetics, Hamilton House, 111 Marlowes, Hemel Hempstead,
    Herts. HP1 1BB
    +44 (0)1442 242 242 Telephonetics - Making Sound Business Sense -
    [url]www.telephonetics.co.uk[/url]

    Telephonetics ContactPortal (R) available now :
    [url]www.telephonetics.co.uk/products/product_contactportal.html[/url]
    Intelligent call routing by spoken voice - just say the name and it dials
    for you. Call me on 01442 242 242 to hear it in action.

    Arrange flower delivery via local florists using the Telephonetics / Web
    Florist service on 08450 111 111 [url]www.webflorists.co.uk/find_a_florist.htm[/url]
    Prompt service anywhere in the UK.

    The disclaimer available at [url]www.telephonetics.co.uk/edisc.html[/url] or by sending
    email
    to <mailto:email-disclaimertelephonetics.co.uk>

    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Pete Dishman Guest

  2. #2

    Default Re: [PHP-DEV] BUG #18630

    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 [url]http://bugs.php.net/bug.php?id=18630[/url] , however the
    > bug was then just closed as a doentation problem and nothing was changed,
    > which is why I'm sending this here rather than adding to the bug report.
    >
    > Anyway, on systems with case-insensitive file systems this problem
    > effectively makes require_once() useless and means you have to rely on code
    > blocks such as:
    > if (defined("ASRD_INCLUDED"))
    > return;
    > define("ASRD_INCLUDED", TRUE);
    >
    > at the top of every single include file, this is definitely ugly and would
    > be much better replaced by require_once().
    > Also using this to prevent multiple inclusions still means that the file
    > will be pd multiple times which is an unnecessary performance drain.
    >
    > >From what I can tell of the code in zend_execute.c, fixing this bug is just
    > a matter of taking a copy of the filename and making it lowercase on windows
    > systems before adding it to the EG(included_files) hashtable.
    >
    > Is there any chance this could be fixed before 4.3.4 is released, as it is
    > definitely a bug and not a doentation problem.
    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).

    About your sig:

    "I wonder if I could request that you ditch the ridiculous ten-line
    ..sig? If not completely, then at least from this list? It's the ASCII
    equivalent of walking out of a public restroom with toilet paper hanging
    out of the back of your pants. The longer it is, the sillier you look."

    Derick

    --
    "Interpreting what the GPL actually means is a job best left to those
    that read the future by examining animal entrails."
    -------------------------------------------------------------------------
    Derick Rethans [url]http://derickrethans.nl/[/url]
    International PHP Magazine [url]http://php-mag.net/[/url]
    -------------------------------------------------------------------------

    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Derick Rethans Guest

  3. #3

    Default RE: [PHP-DEV] BUG #18630

    > 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/diff that changes this behaviour on windows is
    there any
    chance it would be accepted or will the status quo be maintained?

    As for the sig, good point and apologies. It's company policy, but I admit
    I hadn't
    realised how stupid it looks when used in plain text.

    Cheers,
    Pete Dishman

    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Peter Dishman Guest

  4. #4

    Default RE: [PHP-DEV] BUG #18630

    At 04:02 PM 10/29/2003 +0000, 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 enough I
    >suppose.
    >However if I create a patch/diff that changes this behaviour on windows is
    >there any
    >chance it would be accepted or will the status quo be maintained?
    I think it would be a good idea to fix this.
    I'm going to discuss this matter with Zeev and I'll get back to you.

    Andi

    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Andi Gutmans Guest

  5. #5

    Default RE: [PHP-DEV] BUG #18630

    On Wed, 29 Oct 2003, Andi Gutmans wrote:
    > At 04:02 PM 10/29/2003 +0000, 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 enough I
    > >suppose.
    > >However if I create a patch/diff that changes this behaviour on windows is
    > >there any
    > >chance it would be accepted or will the status quo be maintained?
    >
    > I think it would be a good idea to fix this.
    > I'm going to discuss this matter with Zeev and I'll get back to you.
    Isn't this in a hash key which is case sensitive? Then the only
    possibility would be to always lower case it... which is a 'weird' fix
    for this. I really wonder why this should be fixed in code. Why would
    you want to use "require_once("FoO.php"); " in one script, and
    require_once("FOO.PHP") a little bit down? It's just something of
    keeping style in a script which is definitely not a bad thing. I'd say
    that time could better be spend on real fixes...

    Derick

    --
    "Interpreting what the GPL actually means is a job best left to those
    that read the future by examining animal entrails."
    -------------------------------------------------------------------------
    Derick Rethans [url]http://derickrethans.nl/[/url]
    International PHP Magazine [url]http://php-mag.net/[/url]
    -------------------------------------------------------------------------

    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Derick Rethans Guest

  6. #6

    Default RE: [PHP-DEV] BUG #18630

    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 +0000, 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 enough I
    > > >suppose.
    > > >However if I create a patch/diff that changes this behaviour on windows is
    > > >there any
    > > >chance it would be accepted or will the status quo be maintained?
    > >
    > > I think it would be a good idea to fix this.
    > > I'm going to discuss this matter with Zeev and I'll get back to you.
    >
    >Isn't this in a hash key which is case sensitive? Then the only
    >possibility would be to always lower case it... which is a 'weird' fix
    >for this. I really wonder why this should be fixed in code. Why would
    >you want to use "require_once("FoO.php"); " in one script, and
    >require_once("FOO.PHP") a little bit down? It's just something of
    >keeping style in a script which is definitely not a bad thing. I'd say
    >that time could better be spend on real fixes...
    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 good in error messages too.

    Andi

    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Andi Gutmans Guest

  7. #7

    Default RE: [PHP-DEV] BUG #18630

    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 good in error messages too.
    FWIW, Mac OS X is also case-insensative. (As I was reminded of when
    LWP's HEAD overwrote /usr/bin/head and broke everything...)

    -adam

    --
    [email]adamtrachtenberg.com[/email]

    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Adam Maccabee Trachtenberg Guest

  8. #8

    Default RE: [PHP-DEV] BUG #18630

    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 case preserving name). We could then
    > > use that and it would look good in error messages too.
    >
    >FWIW, Mac OS X is also case-insensative. (As I was reminded of when
    >LWP's HEAD overwrote /usr/bin/head and broke everything...)
    Is it case-preserving like Windows? Does realpath work on MAC OS X and give
    the case preserved name?

    Andi

    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Andi Gutmans Guest

  9. #9

    Default Re: [PHP-DEV] BUG #18630

    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:

    [adambenlev:~/Doents/php/test] $ ls -l
    total 0
    -rw-r--r-- 1 adam staff 0 Oct 29 12:10 foo
    [adambenlev:~/Doents/php/test] $ php -r 'print realpath("foo") .
    "\n";'
    /Users/adam/Doents/php/test/foo
    [adambenlev:~/Doents/php/test] $ php -r 'print realpath("FOO") .
    "\n";'
    /Users/adam/Doents/php/test/FOO

    realpath() will return a case-preserved match of the original file, but
    will match the name regardless of case.

    -adam

    --
    adam trachtenberg
    [email]adamtrachtenberg.com[/email]

    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Adam Trachtenberg Guest

  10. #10

    Default Re: [PHP-DEV] BUG #18630

    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
    >answer is yes:
    >
    >[adambenlev:~/Doents/php/test] $ ls -l
    >total 0
    >-rw-r--r-- 1 adam staff 0 Oct 29 12:10 foo
    >[adambenlev:~/Doents/php/test] $ php -r 'print realpath("foo") . "\n";'
    >/Users/adam/Doents/php/test/foo
    >[adambenlev:~/Doents/php/test] $ php -r 'print realpath("FOO") . "\n";'
    >/Users/adam/Doents/php/test/FOO
    >
    >realpath() will return a case-preserved match of the original file, but
    >will match the name regardless of case.
    That's not what I meant. I didn't mean it should preserve the name you pass
    to realpath(). I meant it should give the name which is saved by the OS in
    the filesystem. Win32 is case-insensitive but it does have the case
    preserved version saved.

    Andi

    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Andi Gutmans Guest

  11. #11

    Default Re: [PHP-DEV] BUG #18630

    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 +0000, Pete Dishman wrote:
    >Hi,
    >
    >The fact that require_once()/include_once() are case-sensitive on Windows
    >was reported in bug 18630 [url]http://bugs.php.net/bug.php?id=18630[/url] , however the
    >bug was then just closed as a doentation problem and nothing was changed,
    >which is why I'm sending this here rather than adding to the bug report.
    >
    >Anyway, on systems with case-insensitive file systems this problem
    >effectively makes require_once() useless and means you have to rely on code
    >blocks such as:
    >if (defined("ASRD_INCLUDED"))
    > return;
    >define("ASRD_INCLUDED", TRUE);
    >
    >at the top of every single include file, this is definitely ugly and would
    >be much better replaced by require_once().
    >Also using this to prevent multiple inclusions still means that the file
    >will be pd multiple times which is an unnecessary performance drain.
    >
    > >From what I can tell of the code in zend_execute.c, fixing this bug is just
    >a matter of taking a copy of the filename and making it lowercase on windows
    >systems before adding it to the EG(included_files) hashtable.
    >
    >Is there any chance this could be fixed before 4.3.4 is released, as it is
    >definitely a bug and not a doentation problem.
    >
    >
    >Cheers,
    >Pete Dishman
    >
    >------------------------------------------------
    >
    >Peter Dishman
    >
    >Software Engineer
    >
    >Email: [email]peterdtelephonetics.co.uk[/email]
    >
    >Address: Telephonetics, Hamilton House, 111 Marlowes, Hemel Hempstead,
    >Herts. HP1 1BB
    >+44 (0)1442 242 242 Telephonetics - Making Sound Business Sense -
    >[url]www.telephonetics.co.uk[/url]
    >
    >Telephonetics ContactPortal (R) available now :
    >[url]www.telephonetics.co.uk/products/product_contactportal.html[/url]
    >Intelligent call routing by spoken voice - just say the name and it dials
    >for you. Call me on 01442 242 242 to hear it in action.
    >
    >Arrange flower delivery via local florists using the Telephonetics / Web
    >Florist service on 08450 111 111 [url]www.webflorists.co.uk/find_a_florist.htm[/url]
    >Prompt service anywhere in the UK.
    >
    >The disclaimer available at [url]www.telephonetics.co.uk/edisc.html[/url] or by sending
    >email
    >to <mailto:email-disclaimertelephonetics.co.uk>
    >
    >--
    >PHP Internals - PHP Runtime Development Mailing List
    >To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]
    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Andi Gutmans Guest

  12. #12

    Default Re: [PHP-DEV] BUG #18630

    Forget it. I ed 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 +0000, Pete Dishman wrote:
    >>Hi,
    >>
    >>The fact that require_once()/include_once() are case-sensitive on Windows
    >>was reported in bug 18630 [url]http://bugs.php.net/bug.php?id=18630[/url] , however the
    >>bug was then just closed as a doentation problem and nothing was changed,
    >>which is why I'm sending this here rather than adding to the bug report.
    >>
    >>Anyway, on systems with case-insensitive file systems this problem
    >>effectively makes require_once() useless and means you have to rely on code
    >>blocks such as:
    >>if (defined("ASRD_INCLUDED"))
    >> return;
    >>define("ASRD_INCLUDED", TRUE);
    >>
    >>at the top of every single include file, this is definitely ugly and would
    >>be much better replaced by require_once().
    >>Also using this to prevent multiple inclusions still means that the file
    >>will be pd multiple times which is an unnecessary performance drain.
    >>
    >> >From what I can tell of the code in zend_execute.c, fixing this bug is just
    >>a matter of taking a copy of the filename and making it lowercase on windows
    >>systems before adding it to the EG(included_files) hashtable.
    >>
    >>Is there any chance this could be fixed before 4.3.4 is released, as it is
    >>definitely a bug and not a doentation problem.
    >>
    >>
    >>Cheers,
    >>Pete Dishman
    >>
    >>------------------------------------------------
    >>
    >>Peter Dishman
    >>
    >>Software Engineer
    >>
    >>Email: [email]peterdtelephonetics.co.uk[/email]
    >>
    >>Address: Telephonetics, Hamilton House, 111 Marlowes, Hemel Hempstead,
    >>Herts. HP1 1BB
    >>+44 (0)1442 242 242 Telephonetics - Making Sound Business Sense -
    >>[url]www.telephonetics.co.uk[/url]
    >>
    >>Telephonetics ContactPortal (R) available now :
    >>[url]www.telephonetics.co.uk/products/product_contactportal.html[/url]
    >>Intelligent call routing by spoken voice - just say the name and it dials
    >>for you. Call me on 01442 242 242 to hear it in action.
    >>
    >>Arrange flower delivery via local florists using the Telephonetics / Web
    >>Florist service on 08450 111 111 [url]www.webflorists.co.uk/find_a_florist.htm[/url]
    >>Prompt service anywhere in the UK.
    >>
    >>The disclaimer available at [url]www.telephonetics.co.uk/edisc.html[/url] or by sending
    >>email
    >>to <mailto:email-disclaimertelephonetics.co.uk>
    >>
    >>--
    >>PHP Internals - PHP Runtime Development Mailing List
    >>To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]
    >
    >--
    >PHP Internals - PHP Runtime Development Mailing List
    >To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]
    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Andi Gutmans Guest

  13. #13

    Default Re: [PHP-DEV] BUG #18630

    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 ed 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 +0000, Pete Dishman wrote:
    >>>Hi,
    >>>
    >>>The fact that require_once()/include_once() are case-sensitive on Windows
    >>>was reported in bug 18630 [url]http://bugs.php.net/bug.php?id=18630[/url] , however the
    >>>bug was then just closed as a doentation problem and nothing was changed,
    >>>which is why I'm sending this here rather than adding to the bug report.
    >>>
    >>>Anyway, on systems with case-insensitive file systems this problem
    >>>effectively makes require_once() useless and means you have to rely on code
    >>>blocks such as:
    >>>if (defined("ASRD_INCLUDED"))
    >>> return;
    >>>define("ASRD_INCLUDED", TRUE);
    >>>
    >>>at the top of every single include file, this is definitely ugly and would
    >>>be much better replaced by require_once().
    >>>Also using this to prevent multiple inclusions still means that the file
    >>>will be pd multiple times which is an unnecessary performance drain.
    >>>
    >>> >From what I can tell of the code in zend_execute.c, fixing this bug is
    >>> just
    >>>a matter of taking a copy of the filename and making it lowercase on windows
    >>>systems before adding it to the EG(included_files) hashtable.
    >>>
    >>>Is there any chance this could be fixed before 4.3.4 is released, as it is
    >>>definitely a bug and not a doentation problem.
    >>>
    >>>
    >>>Cheers,
    >>>Pete Dishman
    >>>
    >>>------------------------------------------------
    >>>
    >>>Peter Dishman
    >>>
    >>>Software Engineer
    >>>
    >>>Email: [email]peterdtelephonetics.co.uk[/email]
    >>>
    >>>Address: Telephonetics, Hamilton House, 111 Marlowes, Hemel Hempstead,
    >>>Herts. HP1 1BB
    >>>+44 (0)1442 242 242 Telephonetics - Making Sound Business Sense -
    >>>[url]www.telephonetics.co.uk[/url]
    >>>
    >>>Telephonetics ContactPortal (R) available now :
    >>>[url]www.telephonetics.co.uk/products/product_contactportal.html[/url]
    >>>Intelligent call routing by spoken voice - just say the name and it dials
    >>>for you. Call me on 01442 242 242 to hear it in action.
    >>>
    >>>Arrange flower delivery via local florists using the Telephonetics / Web
    >>>Florist service on 08450 111 111 [url]www.webflorists.co.uk/find_a_florist.htm[/url]
    >>>Prompt service anywhere in the UK.
    >>>
    >>>The disclaimer available at [url]www.telephonetics.co.uk/edisc.html[/url] or by sending
    >>>email
    >>>to <mailto:email-disclaimertelephonetics.co.uk>
    >>>
    >>>--
    >>>PHP Internals - PHP Runtime Development Mailing List
    >>>To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]
    >>
    >>--
    >>PHP Internals - PHP Runtime Development Mailing List
    >>To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]
    >
    >--
    >PHP Internals - PHP Runtime Development Mailing List
    >To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]
    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Andi Gutmans Guest

  14. #14

    Default Re: [PHP-DEV] BUG #18630

    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 and let me know.
    >
    >Andi
    >
    >At 11:17 PM 10/29/2003 +0200, Andi Gutmans wrote:
    >>Forget it. I ed 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 +0000, Pete Dishman wrote:
    >>>>Hi,
    >>>>
    >>>>The fact that require_once()/include_once() are case-sensitive on Windows
    >>>>was reported in bug 18630 [url]http://bugs.php.net/bug.php?id=18630[/url] ,
    >>>>however the
    >>>>bug was then just closed as a doentation problem and nothing was
    >>>>changed,
    >>>>which is why I'm sending this here rather than adding to the bug report.
    >>>>
    >>>>Anyway, on systems with case-insensitive file systems this problem
    >>>>effectively makes require_once() useless and means you have to rely on code
    >>>>blocks such as:
    >>>>if (defined("ASRD_INCLUDED"))
    >>>> return;
    >>>>define("ASRD_INCLUDED", TRUE);
    >>>>
    >>>>at the top of every single include file, this is definitely ugly and would
    >>>>be much better replaced by require_once().
    >>>>Also using this to prevent multiple inclusions still means that the file
    >>>>will be pd multiple times which is an unnecessary performance drain.
    >>>>
    >>>> >From what I can tell of the code in zend_execute.c, fixing this bug
    >>>> is just
    >>>>a matter of taking a copy of the filename and making it lowercase on
    >>>>windows
    >>>>systems before adding it to the EG(included_files) hashtable.
    >>>>
    >>>>Is there any chance this could be fixed before 4.3.4 is released, as it is
    >>>>definitely a bug and not a doentation problem.
    >>>>
    >>>>
    >>>>Cheers,
    >>>>Pete Dishman
    >>>>
    >>>>------------------------------------------------
    >>>>
    >>>>Peter Dishman
    >>>>
    >>>>Software Engineer
    >>>>
    >>>>Email: [email]peterdtelephonetics.co.uk[/email]
    >>>>
    >>>>Address: Telephonetics, Hamilton House, 111 Marlowes, Hemel Hempstead,
    >>>>Herts. HP1 1BB
    >>>>+44 (0)1442 242 242 Telephonetics - Making Sound Business Sense -
    >>>>[url]www.telephonetics.co.uk[/url]
    >>>>
    >>>>Telephonetics ContactPortal (R) available now :
    >>>>[url]www.telephonetics.co.uk/products/product_contactportal.html[/url]
    >>>>Intelligent call routing by spoken voice - just say the name and it dials
    >>>>for you. Call me on 01442 242 242 to hear it in action.
    >>>>
    >>>>Arrange flower delivery via local florists using the Telephonetics / Web
    >>>>Florist service on 08450 111 111 [url]www.webflorists.co.uk/find_a_florist.htm[/url]
    >>>>Prompt service anywhere in the UK.
    >>>>
    >>>>The disclaimer available at [url]www.telephonetics.co.uk/edisc.html[/url] or by
    >>>>sending
    >>>>email
    >>>>to <mailto:email-disclaimertelephonetics.co.uk>
    >>>>
    >>>>--
    >>>>PHP Internals - PHP Runtime Development Mailing List
    >>>>To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]
    >>>
    >>>--
    >>>PHP Internals - PHP Runtime Development Mailing List
    >>>To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]
    >>
    >>--
    >>PHP Internals - PHP Runtime Development Mailing List
    >>To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]
    >
    >--
    >PHP Internals - PHP Runtime Development Mailing List
    >To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]
    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Andi Gutmans Guest

  15. #15

    Default Re: [PHP-DEV] BUG #18630

    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, and NT support is becoming
    incomplete (ext/imap for example does not work on NT).

    Edin

    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Edin Kadribasic Guest

  16. #16

    Default Re: [PHP-DEV] BUG #18630

    >
    > 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 List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Frank M. Kromann Guest

  17. #17

    Default Re: [PHP-DEV] BUG #18630

    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+ s+:+ a-- C++$ UL++++$ P++++ L+++$ E- W++$ N- ?o ?K w--(---)
    !O M+$ V- PS+ PE- Y PGP t++ 5-- X+ R- tv++ b++(+++) DI++++ D+ G++ e+>++
    h(*) r y+(?)

    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Olivier Hill Guest

  18. #18

    Default Re: [PHP-DEV] BUG #18630

    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 doents, where's the cost/benefit in
    upgrading.. :)

    Regards
    Alan

    Edin Kadribasic wrote:
    >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, and NT support is becoming
    >incomplete (ext/imap for example does not work on NT).
    >
    >Edin
    >
    >
    >
    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Alan Knowles Guest

  19. #19

    Default Re: [PHP-DEV] BUG #18630

    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 the top of my head.

    --Wez.

    ----- Original Message -----
    From: "Alan Knowles" <alanakbkhome.com>
    To: "Edin Kadribasic" <edinkproventum.net>
    Cc: "Andi Gutmans" <andizend.com>; "Pete Dishman"
    <peterdtelephonetics.co.uk>; <internalslists.php.net>
    Sent: Wednesday, October 29, 2003 6:20 PM
    Subject: Re: [PHP-DEV] BUG #18630

    > 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 doents, where's the cost/benefit in
    > upgrading.. :)
    >
    > Regards
    > Alan
    >
    > Edin Kadribasic wrote:
    >
    > >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, and NT support is becoming
    > >incomplete (ext/imap for example does not work on NT).
    > >
    > >Edin
    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: http://www.php.net/unsub.php

    Wez Furlong Guest

  20. #20

    Default Re: [PHP-DEV] BUG #18630

    Sorry CVS is a bit of a mystery to me, but I tried
    php-4-win32-STABLE-200310300530.zip from snaps.php.net which didn't work, so
    I then tried php4-200310300830.tar.gz and built it. There was a link error
    relating to php_check_open_basedir_ex() but after working round that the
    test still didn't work.

    Do I take it I'm downloading the wrong things or will your changes not have
    propogated through to snaps.php.net yet?
    and I'm running windows 2000 by the way.

    Cheers,
    Pete Dishman

    "Andi Gutmans" <andizend.com> wrote in message
    news:5.1.0.14.2.20031029233328.032153e8127.0.0.1. ..
    > 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 and let me know.
    > >
    > >Andi
    > >
    > >At 11:17 PM 10/29/2003 +0200, Andi Gutmans wrote:
    > >>Forget it. I ed 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
    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: [url]http://www.php.net/unsub.php[/url]

    Pete Dishman Guest

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139