en.m.wikipedia.org
Case sensitivity
In computers, case sensitivity defines whether uppercase and lowercase letters are treated as distinct (case-sensitive) or equivalent (case-insensitive). For instance, when users interested in learning about dogs search an e-book, "dog" and "Dog" are of the same significance to them. Thus, they request a case-insensitive search. But when they search an online encyclopedia for information about the United Nations, for example, or something with no ambiguity regarding capitalization and ambiguity between two or more terms cut down by capitalization, they may prefer a case-sensitive search.
Areas of significance
Case sensitivity may differ depending on the situation:
In programming languages
Some programming languages are case-sensitive for their identifiers (C, C++, Java, C#, Verilog,[2] Ruby,[3] Python and Swift). Others are case-insensitive (i.e., not case-sensitive), such as ABAP, Ada, most BASICs (an exception being BBC BASIC), Fortran, SQL (for the syntax, and for some vendor implementations, e.g. Microsoft SQL Server, the data itself)[NB 2] and Pascal. There are also languages, such as Haskell, Prolog, and Go, in which the capitalisation of an identifier encodes information about its semantics. Some other programming languages have varying case sensitivity; in PHP, for example, variable names are case-sensitive but function names are not case-sensitive. This means that if you define a function in lowercase, you can call it in uppercase, but if you define a variable in lowercase, you cannot refer to it in uppercase. Nim is case-insensitive and ignores underscores, as long as the first characters match.[4]
In text search
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.[5] In Oracle SQL most operations and searches are case-sensitive by default,[6] while in most other DBMS's SQL searches are case-insensitive by default.[7]
Case-insensitive operations are sometimes said to fold case, from the idea of folding the character code table so that upper- and lowercase letters coincide.
In filesystems
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+ and APFS 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 file systems in other Unix-like environments are case-sensitive, and, for example, a source code tree for software for Unix-like systems might have both a file named Makefile and a file named makefile in the same directory. In addition, some Mac Installers assume case insensitivity and fail on case-sensitive file systems.
The older MS-DOS filesystems FAT12 and FAT16 were 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. Later, with VFAT in Windows 95 the FAT file systems became case-preserving as an extension of supporting Long filenames.[8] 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.[9] This can cause problems for developers or software coming from Unix-like environments, similar to the problems with macOS case-insensitive file systems.
Notes
  1. ^ Note that the link "Friendly Fire" must go through the (disambiguation) qualifier in a Wikipedia article to avoid a WP:INTDAB error.
  2. ^ Although one can explicitly set a single database or column collation to be case-sensitive
References
  1. ^ See WP:DIFFCAPS
  2. ^ Kernighan, Brian W.; Ritchie, Dennis M. (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.
  3. ^ Matsumoto, Yukihiro (January 2002). "Chapter 2: Language Basics". Ruby in a nutshell (1st ed.). O'Reilly Media. p. 9. ISBN 0-596-00214-9.
  4. ^ "Nim Manual: Identifier Equality". nim-lang.github.io. Retrieved 2019-04-27.
  5. ^ "case-sensitive-search - case sensitive google search - Google Project Hosting". code.google.com. Retrieved 2013-05-20.
  6. ^ "2.10 Making Queries Case Insensitive". Oracle SQL Developer User's Guide, Release 1.5(PDF). Oracle Corporation. August 2013.
  7. ^ "MySQL :: MySQL 5.0 Reference Manual :: C.5.5.1 Case Sensitivity in String Searches". dev.mysql.com. Retrieved 2013-05-20.
  8. ^ "Case Sensitivity in Subsystem for UNIX-based Applications". technet.microsoft.com. 2005-08-22. Retrieved 2013-05-20.
  9. ^ "Filenames are Case Sensitive on NTFS Volumes". support.microsoft.com. 2006-11-01. Retrieved 2013-05-20.
Last edited on 16 June 2021, at 09:20
Content is available under CC BY-SA 3.0 unless otherwise noted.
Privacy policy
Terms of Use
Desktop
HomeRandomNearbyLog inSettingsDonateAbout WikipediaDisclaimers
LanguageWatchEdit