php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #37722 spelling of compatibility is wrong for sybase section
Submitted: 2006-06-07 04:15 UTC Modified: 2006-06-07 09:58 UTC
From: timeless at gmail dot com Assigned:
Status: Not a bug Package: PHP options/info functions
PHP Version: 6CVS-2006-06-07 (CVS) OS: linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: timeless at gmail dot com
New email:
PHP Version: OS:

 

 [2006-06-07 04:15 UTC] timeless at gmail dot com 
Description:
------------
http://cvs.php.net/viewcvs.cgi/php-src/php.ini-dist?annotate=1.249#l724

m-w and google offer:
Suggestions for compatability: 
	 1. compatibility

Reproduce code:
---------------
load viewcvs of the current version of php.ini look for Compatability.

I found it a couple of times near:
http://cvs.php.net/viewcvs.cgi/php-src/php.ini-dist?annotate=1.249#l724

Expected result:
----------------
all lines trying to discuss compatibility should consistently spell it correclty

Actual result:
--------------
724 :     ; Compatability mode with old versions of PHP 3.0. 
725 :     ; If on, this will cause PHP to automatically assign types to results according 
726 :     ; to their Sybase type, instead of treating them all as strings.  This 
727 : iliaa 1.222 ; compatibility mode will probably not stay around forever, so try applying 
728 : jon 1.67 ; whatever necessary changes to your code, and turn it off. 
729 :     sybase.compatability_mode = Off

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2006-06-07 07:58 UTC] tony2001@php.net 
See bug #35850.
 [2006-06-07 08:03 UTC] timeless at gmail dot com 
there's no reason not to fix the comments. note that line 727 clearly uses the correct spelling, it's OK to retain the wrong ini item value, but you can still fix the rest of them.
 [2006-06-07 08:07 UTC] tony2001@php.net 
What would fixing comments give us? More confusion? 
No, thanks.
 [2006-06-07 09:58 UTC] timeless at gmail dot com 
you are already inconsistent. There's no reason not to fix the comments and include a note "we're sorry, we goofed, this setting must remain because we published it". Otherwise you will continue to get complaints from people about the improper text sections of your files.

other systems who goof (e.g. referer) internally use the correct spelling and only use the incorrect spelling where they absolutely have to.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Tue Apr 30 00:01:30 2024 UTC