Glob (programming)

{{Short description|Patterns used in computer programming}} {{lowercase title}} {{Use dmy dates|date=July 2019|cs1-dates=y}} [[File:Unix Glob Reference.png|thumb|A screenshot of the original 1971 Unix reference page for <code>glob</code> – the owner is <code>dmr</code>, short for Dennis MacAlistair Ritchie.|class=skin-invert-image]] '''{{mono|glob()}}''' ({{IPAc-en|g|l|ɒ|b}}) is a libc function for '''''globbing''''', which is the archetypal use of pattern matching against the names in a filesystem directory such that a name pattern is expanded into a list of names matching that pattern. Although ''globbing'' may now refer to <code>glob()</code>-style pattern matching of any string, not just expansion into a list of filesystem names, the original meaning of the term is still widespread.

The <code>glob()</code> function and the underlying <code>gmatch()</code><!-- NOT fnmatch(), which first appeared in 4.4BSD --> function originated at Bell Labs in the early 1970s alongside the original AT&T UNIX itself and had a formative influence on the syntax of UNIX command line utilities and therefore also on the present-day reimplementations thereof.

In their original form, <code>glob()</code> and <code>gmatch()</code> derived from code used in Bell Labs in-house utilities that developed alongside the original Unix in the early 1970s. Among those utilities were also two command line tools called <code>glob</code> and <code>find</code>; each could be used to pass a list of matching filenames to other command line tools, and they shared the backend code subsequently formalized as <code>glob()</code> and <code>gmatch()</code>. Shell-statement-level globbing by default became commonplace following the "builtin"-integration of globbing-functionality into the 7th edition of the Unix shell in 1978. The Unix shell's -f option to disable globbing &mdash; i.e. revert to literal "file" mode &mdash; appeared in the same version.

The glob ''pattern quantifiers'' now standardized by POSIX.2 (IEEE Std 1003.2) fall into two groups, and can be applied to any character sequence ("string"), not just to directory entries. * "Metacharacters" (also called "Wildcards"): ** <code>?</code> (not in brackets) matches any character exactly once. ** <code>*</code> (not in brackets) matches a string of zero or more characters. * "Ranges/sets": ** <code><nowiki>[...]</nowiki></code>, where the first character within the brackets is not '!', matches any single character among the characters specified in the brackets. If the first character within brackets is '!', then the <code><nowiki>[!...]</nowiki></code> matches any single character that is ''not'' among the characters specified in the brackets. :: The characters in the brackets may be a list (<code><nowiki>[abc]</nowiki></code>) or a range (<code><nowiki>[a-c]</nowiki></code>) or denote a character class (like <code><nowiki>:space:</nowiki></code> where the inner brackets are part of the classname). POSIX does not mandate multi-range (<code><nowiki>[a-c0-3]</nowiki></code>) support, which derive originally from regular expressions.

As reimplementations of Bell Labs' UNIX proliferated, so did reimplementations of its Bell Labs' libc and shell, and with them <code>glob()</code> and ''globbing''. Today, <code>glob()</code> and ''globbing'' are standardized by the POSIX.2 specification and are integral part of every Unix-like libc ecosystem and shell, including AT&T Bourne shell-compatible Korn shell (ksh), Z shell (zsh), Almquist shell (ash) and its derivatives and reimplementations such as busybox, toybox, GNU bash, Debian dash.

==Origin== The glob command, short for ''global'', originates in the earliest versions of Bell Labs' Unix.<ref name="man7Unix1"/> The command interpreters of the early versions of Unix (1st through 6th Editions, 1969–1975) relied on a separate program to expand wildcard characters in unquoted arguments to a command: ''{{mono|/etc/glob}}''. That program performed the expansion and supplied the expanded list of file paths to the command for execution.

Glob was originally written in the B programming language. It was the first piece of mainline Unix software to be developed in a high-level programming language.<ref name="reader">{{cite tech report |first1=M. D. |last1=McIlroy |author-link1=Doug McIlroy |year=1987 |url=http://www.cs.dartmouth.edu/~doug/reader.pdf |title=A Research Unix reader: annotated excerpts from the Programmer's Manual, 1971–1986 |series=CSTR |number=139 |institution=Bell Labs}}</ref> Later, this functionality was provided as a C library function, <code>glob()</code>, used by programs such as the shell. It is usually defined based on a function named <code>fnmatch()</code>, which tests for whether a string matches a given pattern - the program using this function can then iterate through a series of strings (usually filenames) to determine which ones match. Both functions are a part of POSIX: the functions defined in POSIX.1 since 2001, and the syntax defined in POSIX.2.<ref name=fnmatch3>{{man|3|fnmatch|Linux}}</ref><ref>{{man|3|glob|Linux}}</ref> The idea of defining a separate match function started with wildmat (wildcard match), a simple library to match strings against Bourne Shell globs.

Traditionally, globs do not match hidden files in the form of Unix dotfiles; to match them the pattern must explicitly start with <code>.</code>. For example, <code>*</code> matches all visible files while <code>.*</code> matches all hidden files.

==Syntax==

The most common wildcards are {{code|*}}, {{code|?}}, and {{code|[…]}}.

{| class="wikitable" |- ! Wildcard ! Description ! Example ! Matches ! Does not match

|- | rowspan=2 | {{code|*}} | rowspan=2 | matches any number of any characters including none | {{code|Law*}} | {{code|Law}}, {{code|Laws}}, or {{code|Lawyer}} | {{code|GrokLaw}}, {{code|La}}, or {{code|aw}} |- | {{code|*Law*}} | {{code|Law}}, {{code|GrokLaw}}, or {{code|Lawyer}}. | {{code|La}}, or {{code|aw}} |- | {{code|?}} | matches any single character | {{code|?at}} | {{code|Cat}}, {{code|cat}}, {{code|Bat}} or {{code|bat}} | {{code|at}}

|- | {{code|[abc]}} | matches one character given in the bracket | {{code|[CB]at}} | {{code|Cat}} or {{code|Bat}} | {{code|cat}}, {{code|bat}} or {{code|CBat}}

|- | {{code|[a-z]}} | matches one character from the (locale-dependent) range given in the bracket | {{code|Letter[0-9]}} | {{code|Letter0}}, {{code|Letter1}}, {{code|Letter2}} up to {{code|Letter9}} | {{code|Letters}}, {{code|Letter}} or {{code|Letter10}}

|}

Normally, the path separator character ({{code|/}} on Linux/Unix, MacOS, etc. or {{code|\}} on Windows) will never be matched. Some shells, such as Unix shell have functionality allowing users to circumvent this.<ref>https://www.gnu.org/software/bash/manual/bash.html#Pattern-Matching {{Webarchive|url=https://web.archive.org/web/20180315115230/http://www.gnu.org/software/bash/manual/bash.html#Pattern-Matching |date=2018-03-15 }} Bash Reference Manual</ref>

===Unix-like{{anchor|Unix}}===

On Unix-like systems {{code|*}}, {{code|?}} is defined as above while {{code|[…]}} has two additional meanings:<ref name="posixglob"/><ref name="linuxglob7"/>

{| class="wikitable" |- ! Wildcard ! Description ! Example ! Matches ! Does not match

|- | {{code|[!abc]}} | matches one character that is not given in the bracket | {{code|[!C]at}} | {{code|Bat}}, {{code|bat}}, or {{code|cat}} | {{code|Cat}}

|- | {{code|[!a-z]}} | matches one character that is not from the range given in the bracket | {{code|Letter[!3-5]}} | {{code|Letter1}}, {{code|Letter2}}, {{code|Letter6}} up to {{code|Letter9}} and {{code|Letterx}} etc. | {{code|Letter3}}, {{code|Letter4}}, {{code|Letter5}} or {{code|Letterxx}}

|}

The ranges are also allowed to include pre-defined character classes, equivalence classes for accented characters, and collation symbols for hard-to-type characters. They are defined to match up with the brackets in POSIX regular expressions.<ref name="posixglob"/><ref name="linuxglob7"/>

Unix globbing is handled by the shell per POSIX tradition. Globbing is provided on filenames at the command line and in shell scripts.<ref name="ABSGlob"/> The POSIX-mandated <code>case</code> statement in shells provides pattern-matching using glob patterns.

Some shells (such as the C shell and Bash) support additional syntax known as alternation or brace expansion. Because it is not part of the glob syntax, it is not provided in <code>case</code>. It is only expanded on the command line before globbing.

The Bash shell also supports the following extensions:<ref>{{cite web |title=Bash globs |url=https://mywiki.wooledge.org/glob |website=greg's bash knowledgebase |access-date=25 November 2019 |archive-date=2019-11-18 |archive-url=https://web.archive.org/web/20191118054712/http://mywiki.wooledge.org/glob |url-status=live }}</ref> * Extended globbing (extglob): allows other pattern matching operators to be used to match multiple occurrences of a pattern enclosed in parentheses, essentially providing the missing kleene star and alternation for describing regular languages. It can be enabled by setting the {{code|extglob}} shell option. This option came from ksh93.<ref name="bashpat"/> The GNU fnmatch and glob has an identical extension.<ref name=fnmatch3/> * globstar: allows <code>**</code> on its own as a name component to recursively match any number of layers of non-hidden directories.<ref name="bashpat"/> Also supported by the JavaScript libraries and Python's glob.

===Windows and DOS=== [[File:IBM PC DOS 1.0 screenshot.png|thumb|The {{code|dir}} command with a glob pattern in IBM PC DOS 1.0.]]

The original DOS was a clone of CP/M designed to work on Intel's 8088 and 8086 processors. Windows shells, following DOS, do not traditionally perform any glob expansion in arguments passed to external programs. Shells may use an expansion for their own builtin commands:

* Windows PowerShell has all the common syntax defined as stated above without any additions.<ref name="pwshcmdlet"/> * COMMAND.COM and cmd.exe have most of the common syntax with some limitations: There is no {{code|[…]}} and for COMMAND.COM the {{code|*}} may only appear at the end of the pattern. It can not appear in the middle of a pattern, except immediately preceding the filename extension separator dot.

Windows and DOS programs receive a long command-line string instead of argv-style parameters, and it is their responsibility to perform any splitting, quoting, or glob expansion. There is technically no fixed way of describing wildcards in programs since they are free to do what they wish. Two common glob expanders include:<ref name="winWildcard"/>

* The Microsoft C Runtime (msvcrt) command-line expander, which only supports {{code|?}} and {{code|*}}.<ref>{{cite web |title=Wildcard Expansion |url=https://docs.microsoft.com/en-us/cpp/cpp/wildcard-expansion |website=docs.microsoft.com |date=8 February 2022 |language=en-us}}</ref> Both ReactOS (crt/misc/getargs.c) and Wine (msvcrt/data.c) contain a compatible open-source implementation of {{code|__getmainargs}}, the function operating under-the-hood, in their core CRT. * The Cygwin and MSYS {{code|dcrt0.cc}} command-line expander, which uses the unix-style {{code|glob()}} routine under-the-hood, after splitting the arguments.

Most other parts of Windows, including the Indexing Service, use the MS-DOS style of wildcards found in CMD. A relic of the 8.3 filename age, this syntax pays special attention to dots in the pattern and the text (filename). Internally this is done using three extra wildcard characters, {{code|<>"}}. On the Windows API end, the {{tt|glob()}} equivalent is {{tt|FindFirstFile}}, and {{tt|fnmatch()}} corresponds to its underlying {{tt|RtlIsNameInExpression}}.<ref>[https://blogs.msdn.microsoft.com/jeremykuhne/2017/06/04/wildcards-in-windows/ Wildcards in Windows] {{Webarchive|url=https://web.archive.org/web/20191224091832/https://blogs.msdn.microsoft.com/jeremykuhne/2017/06/04/wildcards-in-windows/ |date=2019-12-24 }}. MSDN Devblog.</ref> (Another fnmatch analogue is {{tt|PathMatchSpec}}.) Both open-source msvcrt expanders use {{tt|FindFirstFile}}, so 8.3 filename quirks will also apply in them.

===SQL=== The SQL {{code|LIKE}} operator has an equivalent to {{code|?}} and {{code|*}} but not {{code|[…]}}.

{| class="wikitable" |- ! Common wildcard ! SQL wildcard ! Description

|- | {{code|?}} | {{code|_}} | matches any single character

|- | {{code|*}} | {{code|%}} | matches any number of any characters including none

|}

Standard SQL uses a glob-like syntax for simple string matching in its <code>LIKE</code> operator, although the term "glob" is not generally used in the SQL community. The percent sign ({{code|%}}) matches zero or more characters and the underscore ({{code|_}}) matches exactly one.

Many implementations of SQL have extended the <code>LIKE</code> operator to allow a richer pattern-matching language, incorporating character ranges ({{code|[…]}}), their negation, and elements of regular expressions.<ref name="transact-sql-like"/>

==Compared to regular expressions== Globs do not include syntax for the Kleene star which allows multiple repetitions of the preceding part of the expression; thus they are not considered regular expressions, which can describe the full set of regular languages over any given finite alphabet.<ref>{{cite book | last1 = Hopcroft | first1 = John E. | last2 = Motwani | first2 = Rajeev | last3 = Ullman | first3 = Jeffrey D. | title = Introduction to Automata Theory, Languages, and Computation | publisher = Addison-Wesley | year = 2000 | edition = 2nd}}</ref>

{| class="wikitable" |- ! Common wildcard ! Equivalent regular expression

|- | {{code|?}} | {{code|.}}

|- | {{code|*}} | {{code|.*}} |}

Globs attempt to match the entire string (for example, {{code|S*.DOC}} matches S.DOC and SA.DOC, but not POST.DOC or SURREY.DOCKS), whereas, depending on implementation details, regular expressions may match a substring.

=== Implementing as regular expressions ===

The original Mozilla proxy auto-config implementation, which provides a glob-matching function on strings, uses a replace-as-RegExp implementation as above. The bracket syntax happens to be covered by regex in such an example.

Python's fnmatch uses a more elaborate procedure to transform the pattern into a regular expression.<ref name=py>{{cite web |title=Lib/fnmatch.py |url=https://github.com/python/cpython/blob/3.8/Lib/fnmatch.py |publisher=Python |access-date=10 November 2021 |date=20 January 2021 |archive-date=2021-11-10 |archive-url=https://web.archive.org/web/20211110204645/https://github.com/python/cpython/blob/3.8/Lib/fnmatch.py |url-status=live }}</ref>

== Other implementations== Beyond their uses in shells, globs patterns also find use in a variety of programming languages, mainly to process human input. A glob-style interface for returning files or an fnmatch-style interface for matching strings are found in the following programming languages:

* C and C++ do not have built-in support for glob patterns in the ISO-defined standard libraries, however on Unix-like systems C and C++ may include <code><glob.h></code> from the C POSIX library to use <code>::glob()</code>. ** C++ itself does not have direct support for glob patterns, however they may be approximated using the <code><filesystem></code> and <code><regex></code> headers, using <code>std::filesystem::directory_iterator</code> and <code>std::regex_match()</code>. ** C++ has external libraries, such as POCO C++ Libraries, which includes a <code>Glob</code> class which can act on glob patterns.<ref>{{cite web|title=Class Poco::Glob|url=https://docs.pocoproject.org/current/Poco.Glob.html|access-date=13 August 2025|website=docs.pocoproject.org}}</ref> * C# provides the official extension library <code>Microsoft.Extensions.FileSystemGlobbing</code>,<ref>{{cite web|title=NuGet Gallery Microsoft.Extensions.FileSystemGlobbing|url=https://www.nuget.org/packages/Microsoft.Extensions.FileSystemGlobbing|access-date=17 August 2025|website=www.nuget.org}}</ref> which contains class <code>Matcher</code>.<ref>{{cite web|title=File globbing in .NET|url=https://learn.microsoft.com/en-us/dotnet/core/extensions/file-globbing|access-date=17 August 2025|website=learn.microsoft.com}}</ref> ** C# also has multiple external libraries available through NuGet such as <code>Glob</code><ref name="dotnet-glob"/> or <code>DotNet.Glob</code>.<ref name="dotnet.glob"/> * D has a <code>globMatch</code> function in the <code>std.path</code> module.<ref name="dlang"/> * Go has a <code>Glob</code> function in the <code>filepath</code> package.<ref name="golang"/> * Java provides package <code>java.nio.file</code> which contains class <code>Files</code>,<ref name="java"/> which has methods such as <syntaxhighlight lang="java" inline>Files.newDirectoryStream(Path dir, String glob)</syntaxhighlight> for operating over glob patterns and returns <code>DirectoryStream<Path></code>. The package also contains the classes <code>FileSystems</code> and <code>PathMatcher</code> for matching glob patterns. * Haskell has a <code>Glob</code> package with the main module <code>System.FilePath.Glob</code>. The pattern syntax is based on a subset of Zsh's. It tries to optimize the given pattern and should be noticeably faster than a naïve character-by-character matcher.<ref name="hs"/> * Node.js has a <code>glob</code> function in the <code>node:fs</code> module.<ref name="nodejs"/> * Perl has both a <code>glob</code> function (as discussed in Larry Wall's book ''Programming Perl'') and a ''Glob'' extension which mimics the BSD glob routine.<ref name="pl"/> Perl's angle brackets can be used to glob as well: <code>&lt;*.log&gt;</code>. * PHP has a <code>glob</code> function.<ref name="php"/> * Python has a <code>glob</code> module in the standard library which performs wildcard pattern matching on filenames,<ref name="pyglob"/> and an <code>fnmatch</code> module with functions for matching strings or filtering lists based on these same wildcard patterns.<ref name=py/> Guido van Rossum, author of the Python programming language, wrote and contributed a <code>glob</code> routine to BSD Unix in 1986.<ref name="isc-glob"/> There were previous implementations of <code>glob</code>, e.g., in the ex and ftp programs in previous releases of BSD. * Ruby has a <code>glob</code> method for the <code>Dir</code> class which performs wildcard pattern matching on filenames.<ref name="rbdir"/> Several libraries such as Rant and Rake provide a <code>FileList</code> class which has a glob method or use the method <code>FileList.[]</code> identically. * Rust has multiple libraries that can match glob patterns,<ref>{{cite web|title=#glob - Lib.rs|url=https://lib.rs/keywords/glob|access-date=12 November 2021|website=lib.rs|archive-date=2021-11-12 |archive-url=https://web.archive.org/web/20211112115505/https://lib.rs/keywords/glob|url-status=live}}</ref> the most popular of these being the <code>glob</code> crate which itself has a <code>glob()</code> function.<ref>{{cite web|title=glob - Lib.rs|url=https://lib.rs/crates/glob|access-date=17 January 2025|website=lib.rs}}</ref> * SQLite has a <code>GLOB</code> function. * Tcl contains a globbing facility.<ref name="tcl"/>

==See also== * Regular expression * Wildcard character * Matching wildcards

==References== {{Reflist|refs= <ref name="man7Unix1">{{cite web |url=http://cm.bell-labs.com/cm/cs/who/dmr/man71.pdf |archive-url=https://web.archive.org/web/20000829224359/http://cm.bell-labs.com/cm/cs/who/dmr/man71.pdf |url-status=dead |archive-date=2000-08-29 |title=First Edition Unix manual 'Miscellaneous' section (PDF) |access-date=2011-05-11}}</ref> <ref name="posixglob">{{cite web |title=The Open Group Base Specifications Issue 7 IEEE Std 1003.1, 2013 Edition, 2.13. Pattern Matching Notation |url=http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_13 |access-date=2015-10-26 |archive-date=2014-04-27 |archive-url=https://web.archive.org/web/20140427082439/http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_13 |url-status=live }}</ref> <ref name="linuxglob7">{{cite web |title=Linux Programmer's Manual, GLOB(7) |url=http://man7.org/linux/man-pages/man7/glob.7.html |access-date=2015-10-26 |archive-date=2015-10-31 |archive-url=https://web.archive.org/web/20151031215157/http://man7.org/linux/man-pages/man7/glob.7.html |url-status=live }}</ref> <ref name="bashpat">{{cite web |website=Bash Reference Manual |title=Pattern Matching |url=https://www.gnu.org/software/bash/manual/html_node/Pattern-Matching.html |access-date=2016-01-11 |archive-date=2016-02-11 |archive-url=https://web.archive.org/web/20160211205104/http://www.gnu.org/software/bash/manual/html_node/Pattern-Matching.html |url-status=live }}</ref> <ref name="pwshcmdlet">{{cite web |title=Supporting Wildcard Characters in Cmdlet Parameters |url=https://docs.microsoft.com/en-us/powershell/scripting/developer/cmdlet/supporting-wildcard-characters-in-cmdlet-parameters|publisher=Microsoft Developer Network |website=Microsoft|date=18 December 2023 }}</ref> <ref name="transact-sql-like">{{cite web |title=LIKE (Transact-SQL) |date=23 May 2023 |url=https://docs.microsoft.com/en-us/sql/t-sql/language-elements/like-transact-sql |access-date=2017-08-01 |archive-date=2017-08-02 |archive-url=https://web.archive.org/web/20170802044711/https://docs.microsoft.com/en-us/sql/t-sql/language-elements/like-transact-sql |url-status=live }}</ref> <ref name="ABSGlob">The "Advanced Bash-Scripting Guide, Chapter 19.2: Globbing" (Mendel Cooper, 2003) has a concise set of examples of filename globbing patterns.</ref> <ref name="winWildcard">{{cite web |url=http://msdn.microsoft.com/en-us/library/e1w828yy.aspx |title=Wildcard Expansion |publisher=Microsoft Developer Network |year=2013 |access-date=2013-10-16 |archive-date=2014-08-22 |archive-url=https://web.archive.org/web/20140822042708/http://msdn.microsoft.com/en-us/library/e1w828yy.aspx |url-status=live }}</ref> <!-- unused ref <ref name="winWcExp">{{cite web |url=http://msdn.microsoft.com/en-us/library/8bch7bkk.aspx |title=Expanding Wildcard Arguments |publisher=Microsoft Developer Network |date=2013}}</ref> --> <ref name="dlang">{{cite web |url=http://dlang.org/phobos/std_path.html#.globMatch |title=std.path - D Programming Language - Digital Mars |publisher=dlang.org |access-date=2014-09-08 |archive-date=2014-09-08 |archive-url=https://web.archive.org/web/20140908203040/http://dlang.org/phobos/std_path.html#.globMatch |url-status=live }}</ref> <ref name="golang">{{cite web |url=http://golang.org/pkg/path/filepath/#Glob |title=Package filepath - The Go Programming Language |publisher=Golang.org |access-date=2011-05-11 |archive-date=2011-05-25 |archive-url=https://web.archive.org/web/20110525035625/http://golang.org/pkg/path/filepath/#Glob |url-status=live }}</ref> <ref name="java">{{cite web |url=http://docs.oracle.com/javase/tutorial/essential/io/fileOps.html#glob |title=File Operations |publisher=Oracle |access-date=2013-12-16 |archive-date=2013-09-20 |archive-url=https://web.archive.org/web/20130920172102/http://docs.oracle.com/javase/tutorial/essential/io/fileOps.html#glob |url-status=live }}</ref> <ref name="hs">{{cite web |url=http://hackage.haskell.org/package/Glob-0.7.4/docs/System-FilePath-Glob.html |title=Glob-0.7.4: Globbing library |access-date=2014-05-07 |archive-date=2014-05-08 |archive-url=https://web.archive.org/web/20140508025811/http://hackage.haskell.org/package/Glob-0.7.4/docs/System-FilePath-Glob.html |url-status=live }}</ref> <ref name="nodejs">{{cite web |url=https://nodejs.org/docs/latest/api/fs.html#fspromisesglobpattern-options |title=File system - Node.js Documentation |access-date=2025-07-16 |archive-date=2025-07-16 |archive-url=https://web.archive.org/web/20250716040734/https://nodejs.org/docs/latest/api/fs.html#fspromisesglobpattern-options |url-status=live }}</ref> <ref name="pl">{{cite web |url=http://perldoc.perl.org/File/Glob.html |title=File::Glob - Perl extension for BSD glob routine |publisher=perldoc.perl.org |access-date=2011-05-11}}</ref> <ref name="php">{{cite web |url=http://www.php.net/glob |title=glob - Manual |publisher=PHP |date=2011-05-06 |access-date=2011-05-11 |archive-date=2017-11-13 |archive-url=https://web.archive.org/web/20171113011131/http://php.net/glob |url-status=live }}</ref> <ref name="pyglob">{{cite web |url=https://docs.python.org/library/glob.html |title=10.7. glob — Unix style pathname pattern expansion — Python v2.7.1 documentation |publisher=Docs.python.org |access-date=2011-05-11 |archive-date=2011-05-16 |archive-url=https://web.archive.org/web/20110516205728/http://docs.python.org/library/glob.html |url-status=live }}</ref> <ref name="isc-glob">{{cite web |url=http://www.isc.org/sources/devel/func/glob.txt |title='Globbing' library routine |access-date=2011-05-11 |archive-url=https://web.archive.org/web/20071219090708/http://www.isc.org/sources/devel/func/glob.txt |archive-date=2007-12-19}}</ref> <ref name="rbdir">{{cite web |url=https://docs.ruby-lang.org/en/master/Dir.html |title=Class: Dir |publisher=Ruby-doc.org |access-date=2011-05-11 |archive-date=2011-05-15 |archive-url=https://web.archive.org/web/20110515140813/http://ruby-doc.org/core/classes/Dir.html#M000629 |url-status=live }}</ref> <ref name="tcl">{{cite web |url=http://www.tcl.tk/man/tcl8.5/TclCmd/glob.htm |title=TCL glob manual page |access-date=2011-11-16 |archive-date=2011-12-08 |archive-url=https://web.archive.org/web/20111208112250/http://www.tcl.tk/man/tcl8.5/TclCmd/glob.htm |url-status=live }}</ref> <ref name="dotnet-glob">{{Cite web |url=https://github.com/kthompson/glob |title=kthompson/glob |website=GitHub |access-date=2020-11-06 |archive-date=2020-10-26 |archive-url=https://web.archive.org/web/20201026174625/https://github.com/kthompson/glob |url-status=live }}</ref> <ref name="dotnet.glob">{{Cite web |url=https://github.com/dazinator/DotNet.Glob |title=dazinator/dotnet.glob |website=GitHub |access-date=2022-06-22 |archive-date=2022-06-22 |archive-url=https://web.archive.org/web/20220622181350/https://github.com/dazinator/DotNet.Glob |url-status=live }}</ref> }}

Category:C POSIX library Category:Pattern matching Category:Unix programming tools