{"id":4724,"date":"2022-12-20T18:36:49","date_gmt":"2022-12-20T21:36:49","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/fnmatch-man3p\/"},"modified":"2022-12-20T18:36:49","modified_gmt":"2022-12-20T21:36:49","slug":"fnmatch-man3p","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/fnmatch-man3p\/","title":{"rendered":"FNMATCH (man3p)"},"content":{"rendered":"

FNMATCH<\/h1>\n

PROLOG<\/a>
NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
RETURN VALUE<\/a>
ERRORS<\/a>
EXAMPLES<\/a>
APPLICATION USAGE<\/a>
RATIONALE<\/a>
FUTURE DIRECTIONS<\/a>
SEE ALSO<\/a>
COPYRIGHT<\/a> <\/p>\n

\n

PROLOG <\/a> <\/h2>\n

This manual page is part of the POSIX Programmer\u2019s Manual. The Linux implementation of this interface may differ (consult the corresponding Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux.<\/p>\n

NAME <\/a> <\/h2>\n

fnmatch \u2014 match a filename string or a pathname<\/p>\n

SYNOPSIS <\/a> <\/h2>\n

#include <\/p>\n

int fnmatch(const char *pattern<\/i>, const char *string<\/i>, int flags<\/i>);<\/p>\n

DESCRIPTION <\/a> <\/h2>\n

The fnmatch<\/i>() function shall match patterns as described in the Shell and Utilities volume of POSIX.1-2017, Section 2.13.1<\/i>, Patterns Matching a Single Character<\/i> and Section 2.13.2<\/i>, Patterns Matching Multiple Characters<\/i>. It checks the string specified by the string<\/i> argument to see if it matches the pattern specified by the pattern<\/i> argument.<\/p>\n

The flags<\/i> argument shall modify the interpretation of pattern<\/i> and string<\/i>. It is the bitwise-inclusive OR of zero or more of the flags defined in <\/i>. If the FNM_PATHNAME flag is set in flags<\/i>, then a character (\u2019\/\u2019<\/b>) in string<\/i> shall be explicitly matched by a in pattern<\/i>; it shall not be matched by either the or special characters, nor by a bracket expression. If the FNM_PATHNAME flag is not set, the character shall be treated as an ordinary character.<\/p>\n

If FNM_NOESCAPE is not set in flags<\/i>, a character in pattern<\/i> followed by any other character shall match that second character in string<\/i>. In particular, “\\”<\/b> shall match a in string<\/i>. If pattern<\/i> ends with an unescaped , fnmatch<\/i>() shall return a non-zero value (indicating either no match or an error). If FNM_NOESCAPE is set, a character shall be treated as an ordinary character.<\/p>\n

If FNM_PERIOD is set in flags<\/i>, then a leading (\u2019.\u2019<\/b>) in string<\/i> shall match a in pattern<\/i>; as described by rule 2 in the Shell and Utilities volume of POSIX.1-2017, Section 2.13.3<\/i>, Patterns Used for Filename Expansion<\/i> where the location of \u2018\u2018leading\u2019\u2019 is indicated by the value of FNM_PATHNAME:<\/p>\n\n\n\n
<\/td>\n\n

*<\/p>\n<\/td>\n

<\/td>\n\n

If FNM_PATHNAME is set, a is \u2018\u2018leading\u2019\u2019 if it is the first character in string<\/i> or if it immediately follows a .<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

*<\/p>\n<\/td>\n

<\/td>\n\n

If FNM_PATHNAME is not set, a is \u2018\u2018leading\u2019\u2019 only if it is the first character of string<\/i>.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

If FNM_PERIOD is not set, then no special restrictions are placed on matching a period.<\/p>\n

RETURN VALUE <\/a> <\/h2>\n

If string<\/i> matches the pattern specified by pattern<\/i>, then fnmatch<\/i>() shall return 0. If there is no match, fnmatch<\/i>() shall return FNM_NOMATCH, which is defined in <\/i>. If an error occurs, fnmatch<\/i>() shall return another non-zero value.<\/p>\n

ERRORS <\/a> <\/h2>\n

No errors are defined.<\/p>\n

The following sections are informative.<\/i><\/p>\n

EXAMPLES <\/a> <\/h2>\n

None.<\/p>\n

APPLICATION USAGE <\/a> <\/h2>\n

The fnmatch<\/i>() function has two major uses. It could be used by an application or utility that needs to read a directory and apply a pattern against each entry. The find<\/i> utility is an example of this. It can also be used by the pax<\/i> utility to process its pattern<\/i> operands, or by applications that need to match strings in a similar manner.<\/p>\n

The name fnmatch<\/i>() is intended to imply filename<\/i> match, rather than pathname<\/i> match. The default action of this function is to match filename strings, rather than pathnames, since it gives no special significance to the character. With the FNM_PATHNAME flag, fnmatch<\/i>() does match pathnames, but without tilde expansion, parameter expansion, or special treatment for a at the beginning of a filename.<\/p>\n

RATIONALE <\/a> <\/h2>\n

This function replaced the REG_FILENAME flag of regcomp<\/i>() in early proposals of this volume of POSIX.1-2017. It provides virtually the same functionality as the regcomp<\/i>() and regexec<\/i>() functions using the REG_FILENAME and REG_FSLASH flags (the REG_FSLASH flag was proposed for regcomp<\/i>(), and would have had the opposite effect from FNM_PATHNAME), but with a simpler function and less system overhead.<\/p>\n

FUTURE DIRECTIONS <\/a> <\/h2>\n

None.<\/p>\n

SEE ALSO <\/a> <\/h2>\n

glob<\/i>(), Section 2.6<\/i>, Word Expansions<\/i><\/p>\n

The Base Definitions volume of POSIX.1-2017, <\/b><\/p>\n

COPYRIGHT <\/a> <\/h2>\n

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology — Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http:\/\/www.opengroup.org\/unix\/online.html .<\/p>\n

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https:\/\/www.kernel.org\/doc\/man-pages\/reporting_bugs.html .<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

fnmatch \u2014 match a filename string or a pathname <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3779,1],"tags":[1645,1594],"class_list":["post-4724","post","type-post","status-publish","format-standard","hentry","category-3pm-perl-llamadas-de-bibliotecas","category-sin-categoria","tag-fnmatch","tag-man3p"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4724","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=4724"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4724\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=4724"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=4724"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=4724"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}