Case sensitivity

Last updated on 2 November 2017

In computers, upper case and lower case text may be treated as distinct (case sensitivity) or equivalent (case insensitivity). For example, the following are sometimes case-sensitive, sometimes not:

Some programming languages are case-sensitive for their identifiers (C, C++, Java, C#, Verilog,[1] Ruby[2] and XML). Others are case-insensitive (i.e., not case-sensitive), such as Ada, most BASICs (an exception being BBC BASIC), Fortran, SQL[3] and Pascal. There are also languages, such as Haskell, Prolog and Go, in which the capitalization of an identifier encodes information about its semantics.

A text search operation could be case-sensitive or case-insensitive, depending on the system, application, or context. The user can in many cases specify whether a search is sensitive to case, e.g. in most text editors, word processors, and Web browsers. A case-insensitive search is more comprehensive, finding "Language" (at the beginning of a sentence), "language", and "LANGUAGE" (in a title in capitals); a case-sensitive search will find the computer language "BASIC" but exclude most of the many unwanted instances of the word. For example, the Google search engine is basically case-insensitive, with no option for case-sensitive search.[4] In Oracle SQL most operations and searches are case-sensitive by default,[5] while in most other DBMS's SQL searches are case-insensitive by default.[6]

Case-insensitive operations are sometimes said to fold case, from the idea of folding the character code table so that upper- and lower-case letters coincide.

In filesystems in Unix-like systems, filenames are usually case-sensitive (there can be separate readme.txt and Readme.txt files in the same directory). macOS is somewhat unusual in that, by default, it uses HFS+ in a case-insensitive (so that there cannot be a readme.txt and a Readme.txt in the same directory) but case-preserving mode (so that a file created as readme.txt is shown as readme.txt and a file created as Readme.txt is shown as Readme.txt) by default. This causes some issues for developers and power users, because most other environments are case sensitive, but many Mac Installers fail on case sensitive file systems.

The older Microsoft Windows filesystems VFAT and FAT32 are not case-sensitive, but are case-preserving. The earlier FAT12 filesystem was case-insensitive and not case-preserving, so that a file whose name is entered as readme.txt or ReadMe.txt is saved as README.TXT.[7] Later Windows file systems such as NTFS are internally case-sensitive, and a readme.txt and a Readme.txt can coexist in the same directory. However, for practical purposes filenames behave as case-insensitive as far as users and most software are concerned.[8]

References

  1. ^ Kernighan, Brian W.; Dennis M. Ritchie (February 1978). "Chapter 2: Types, Operators and Expressions". The C Programming Language (1st ed.). Englewood Cliffs, NJ: Prentice Hall. p. 33. ISBN 0-13-110163-3.
  2. ^ Matsumoto, Yukihiro (January 2002). "Chapter 2: Language Basics". Ruby in a nutshell (1st ed.). O'Reilly Media. p. 9. ISBN 0-596-00214-9.
  3. ^ Although one can explicitly set a single database or column collation to be case-sensitive
  4. ^ "case-sensitive-search - case sensitive google search - Google Project Hosting". Code.google.com. Retrieved 2013-05-20.
  5. ^ http://docs.oracle.com/cd/E12151_01/doc.150/e12152.pdf#page=103
  6. ^ "MySQL :: MySQL 5.0 Reference Manual :: C.5.5.1 Case Sensitivity in String Searches". Dev.mysql.com. Retrieved 2013-05-20.
  7. ^ "Case Sensitivity in Subsystem for UNIX-based Applications". Technet.microsoft.com. 2005-08-22. Retrieved 2013-05-20.
  8. ^ "Filenames are Case Sensitive on NTFS Volumes". Support.microsoft.com. 2006-11-01. Retrieved 2013-05-20.

This page is based on a Wikipedia article written by authors (here).
Text is available under the CC BY-SA 3.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.