Jak ja nienawidzę protekcjonalności…

  •  

    #oglaszamwszemiwobec że @MajkiGee to gimbokatol najczystszej wody. Troskę o zdrowie fizyczne i psychiczne dzieci nazywa gimboateizmem. On jest już stracony. #obrazamludziktorzymajamnienaczarnolisto #gimbokatolicyzm

    +: wuha, Cronox
  •  

    #niepopularnaopinia Uważam, że @Klopsztanga zrobił dobrze, chroniąc niewinnego chłopaka przed nabyciem poroża
    @Xanthia:

    pokaż spoiler Nasyp sobie soli


    pokaż spoiler Sama wiesz, gdzie

  •  

    @l__g: Jak rozwiązaliście sprawę z "nową wersją" i "starą wersją" wykopu? Są to oddzielne apki, na które requesty routuje jakieś proxy, czy może jest to jedna apka? Ciekawi mnie, jak to rozwiązaliście.

    +: Cronox
  •  

    Drodzy @Envelo, czemu "Doręczenie na życzenie" jest takie drogie? Choremu człowiekowi to nic nie pomożecie ;__; #pocztapolska

    +: Cronox
  •  

    #niepopularnaopinia #chrzescijanstwo #islam

    Półksiężyc jest znacznie lepszym symbolem, niż krzyż. Krzyż to narzędzie śmierci, symbolizuje cierpienie. Półksiężyc to po prostu nieszkodliwy element naszego kosmosu.

    +: Cronox
  •  

    #nofapchallenge

    Kiedyś próbowałem tego wyzwania. Podczas wielu prób zastanawiała mnie jedna rzecz: czy spuszczanie ciśnienia do narysowanych postaci z anime wymusza reset licznika? W sumie nie jest to tak jakby prawdziwe porno.

    +: Cronox
  •  

    Ma ktoś prawilnego ebooka "Pan raczy żartować, panie Feynman", czy zostaje mi czytać z Amazon.com po angielsku?

    #wykopkindleclub

    +: Cronox
  •  

    Czy wy też tak macie, że im bardziej chce się wam spać, tym większe głupoty gadacie i wymyślacie? #pyciochkita #pytanie #wkurzajacaprotekcjonalnosc

  •  

    Dziwne, chce mi się spać szybciej, niż zwykle, ale nie tak, że ziewam i te klimaty, tylko normalnie jakbym był o krok od zaśnięcia. Pewnie jak się położę w pielesze to będę kontemplował życiasens i nie zasnę. #problemydrugiegoswiata #sen #niespimymirkujemy #ironialosu #wkurzajacaprotekcjonalnosc pokaż całość

  •  

    Ciekawe jest dwójmyślenie wykopu.
    Muzułmanie indoktrynują małe dzieci — źle
    Katolicy indoktrynują małe dzieci — dobrze

    #plemiennosc #katolicyzm #islam #religia #wykop #gimbokatolicyzm #dwojmyslenie #moralnosckalego

    +: Cronox
  •  

    #nowywykop2016 Przydałyby się powiadomienia o tym, że moderacja wymoderowała naszą treść, a także powiadomienia o rozpatrzeniu zgłoszeń

  •  

    Chciałem ci powiedzieć, @dkm17, że robisz dobrą robotę. Nie przestawaj, jestem twoim fanem. #unb #uwaganaukowybelkot #podlizujesie

  •  

    #myslispodprysznica #showerthoughts #rozkmina #elektryka #elektroenergetyka

    Jeden z członków mojej rodziny podsunął mi pewną rozkminę: co, jeśli nagle pracownicy elektrowni będą mieli dość obecnych rządów i tzw. "wykształciuchów", i wygaszą taką przeciętną, węglową elektrownię tak, że nie będzie ona dostarczała kompletnie prądu, ani miliwata? Co się wtedy stanie? Podejrzewam, że jakiś blackout, ale jak długi, i na jakim obszarze? Jak zareaguje sieć energetyczna? No i jakie mogą być tego czynu konsekwencje czysto prawne? (Czyżby ABW karabinem zmuszająca do wznowienia pracy elektrowni) pokaż całość

    +: N..H, Cronox
  •  

    1 A wąż1 był bardziej przebiegły niż wszystkie zwierzęta lądowe, które Pan Bóg stworzył. On to rzekł do niewiasty: «Czy rzeczywiście Bóg powiedział: Nie jedzcie owoców ze wszystkich drzew tego ogrodu?» 2 Niewiasta odpowiedziała wężowi: «Owoce z drzew tego ogrodu jeść możemy, 3 tylko o owocach z drzewa, które jest w środku ogrodu, Bóg powiedział: Nie wolno wam jeść z niego, a nawet go dotykać, abyście nie pomarli». 4 Wtedy rzekł wąż do niewiasty: «Na pewno nie umrzecie! 5 Ale wie Bóg, że gdy spożyjecie owoc z tego drzewa, otworzą się wam oczy i tak jak Bóg będziecie znali dobro i zło».
    6 Wtedy niewiasta spostrzegła, że drzewo to ma owoce dobre do jedzenia, że jest ono rozkoszą dla oczu i że owoce tego drzewa nadają się do zdobycia wiedzy. Zerwała zatem z niego owoc, skosztowała i dała swemu mężowi, który był z nią: a on zjadł. 7 A wtedy otworzyły się im obojgu oczy i poznali, że są nadzy; spletli więc gałązki figowe i zrobili sobie przepaski.
    8 Gdy zaś mężczyzna i jego żona usłyszeli kroki Pana Boga przechadzającego się po ogrodzie, w porze kiedy był powiew wiatru, skryli się przed Panem Bogiem wśród drzew ogrodu. 9 Pan Bóg zawołał na mężczyznę i zapytał go: «Gdzie jesteś?» 10 On odpowiedział: «Usłyszałem Twój głos w ogrodzie, przestraszyłem się, bo jestem nagi, i ukryłem się». 11 Rzekł Bóg: «Któż ci powiedział, że jesteś nagi? Czy może zjadłeś z drzewa, z którego ci zakazałem jeść?» 12 Mężczyzna odpowiedział: «Niewiasta, którą postawiłeś przy mnie, dała mi owoc z tego drzewa i zjadłem». 13 Wtedy Pan Bóg rzekł do niewiasty: «Dlaczego to uczyniłaś?» Niewiasta odpowiedziała: «Wąż mnie zwiódł i zjadłam». 14 Wtedy Pan Bóg rzekł do węża:
    «Ponieważ to uczyniłeś,
    bądź przeklęty wśród wszystkich zwierząt domowych i polnych;
    na brzuchu będziesz się czołgał i proch będziesz jadł po wszystkie dni twego istnienia.
    15 Wprowadzam nieprzyjaźń między ciebie i niewiastę,
    pomiędzy potomstwo twoje a potomstwo jej:
    ono zmiażdży2 ci głowę,
    a ty zmiażdżysz2 mu piętę».
    16 Do niewiasty powiedział: «Obarczę cię niezmiernie wielkim trudem twej brzemienności, w bólu będziesz rodziła dzieci, ku twemu mężowi będziesz kierowała swe pragnienia, on zaś będzie panował nad tobą».
    17 Do mężczyzny zaś [Bóg] rzekł: «Ponieważ posłuchałeś swej żony i zjadłeś z drzewa, co do którego dałem ci rozkaz w słowach: Nie będziesz z niego jeść -
    przeklęta3 niech będzie ziemia z twego powodu:
    w trudzie będziesz zdobywał od niej pożywienie dla siebie
    po wszystkie dni twego życia.
    18 Cierń i oset będzie ci ona rodziła,
    a przecież pokarmem twym są płody roli.
    19 W pocie więc oblicza twego
    będziesz musiał zdobywać pożywienie,
    póki nie wrócisz do ziemi,
    z której zostałeś wzięty;
    bo prochem jesteś
    i w proch się obrócisz!»4
    20 Mężczyzna dał swej żonie imię Ewa5, bo ona stała się matką wszystkich żyjących.
    21 Pan Bóg sporządził dla mężczyzny i dla jego żony odzienie ze skór i przyodział ich. 22 Po czym Pan Bóg rzekł: «Oto człowiek stał się taki jak My: zna dobro i zło; niechaj teraz nie wyciągnie przypadkiem ręki, aby zerwać owoc także z drzewa życia, zjeść go i żyć na wieki»6. 23 Dlatego Pan Bóg wydalił go z ogrodu Eden, aby uprawiał tę ziemię, z której został wzięty. 24 Wygnawszy zaś człowieka, Bóg postawił przed ogrodem Eden cherubów i połyskujące ostrze miecza, aby strzec drogi do drzewa życia7.
    pokaż całość

    +: Cronox
  •  

    1 W ten sposób zostały ukończone niebo i ziemia oraz wszystkie jej zastępy [stworzeń].
    2 A gdy Bóg ukończył w dniu szóstym swe dzieło, nad którym pracował, odpoczął1 dnia siódmego po całym swym trudzie, jaki podjął. 3 Wtedy Bóg pobłogosławił ów siódmy dzień i uczynił go świętym; w tym bowiem dniu odpoczął po całej swej pracy, którą wykonał stwarzając.
    4 Oto są dzieje początków po stworzeniu nieba i ziemi.

    Drugi opis stworzenia człowieka

    Gdy Pan2 Bóg uczynił ziemię i niebo, 5 nie było jeszcze żadnego krzewu polnego na ziemi, ani żadna trawa polna jeszcze nie wzeszła - bo Pan Bóg nie zsyłał deszczu na ziemię i nie było człowieka, który by uprawiał ziemię 6 i rów kopał w ziemi3, aby w ten sposób nawadniać całą powierzchnię gleby - 7 wtedy to Pan Bóg ulepił człowieka z prochu ziemi i tchnął w jego nozdrza tchnienie życia4, wskutek czego stał się człowiek istotą żywą.

    Pierwotny stan szczęścia

    8 A zasadziwszy ogród w Eden5 na wschodzie, Pan Bóg umieścił tam człowieka, którego ulepił. 9 Na rozkaz Pana Boga wyrosły z gleby wszelkie drzewa miłe z wyglądu i smaczny owoc rodzące oraz drzewo życia w środku tego ogrodu i drzewo poznania dobra i zła6.
    10 Z Edenu zaś wypływała rzeka, aby nawadniać ów ogród, i stamtąd się rozdzielała, dając początek czterem rzekom7. 11 Nazwa pierwszej - Piszon; jest to ta, która okrąża cały kraj Chawila, gdzie się znajduje złoto. 12 A złoto owej krainy jest znakomite; tam jest także wonna żywica i kamień czerwony. 13 Nazwa drugiej rzeki - Gichon; okrąża ona cały kraj - Kusz. 14 Nazwa rzeki trzeciej - Chiddekel; płynie ona na wschód od Aszszuru. Rzeka czwarta - to Perat.
    15 Pan Bóg wziął zatem człowieka i umieścił go w ogrodzie Eden, aby uprawiał go i doglądał. 16 A przy tym Pan Bóg dał człowiekowi taki rozkaz: «Z wszelkiego drzewa tego ogrodu możesz spożywać według upodobania; 17 ale z drzewa poznania dobra i zła nie wolno ci jeść, bo gdy z niego spożyjesz, niechybnie umrzesz»8.
    18 Potem Pan Bóg rzekł: «Nie jest dobrze, żeby mężczyzna był sam, uczynię mu zatem odpowiednią dla niego pomoc». 19 Ulepiwszy z gleby wszelkie zwierzęta lądowe i wszelkie ptaki powietrzne, Pan Bóg przyprowadził je do mężczyzny, aby przekonać się, jaką on da im nazwę. Każde jednak zwierzę, które określił mężczyzna, otrzymało nazwę "istota żywa"9. 20 I tak mężczyzna dał nazwy wszelkiemu bydłu, ptakom powietrznym i wszelkiemu zwierzęciu polnemu, ale nie znalazła się pomoc odpowiednia dla mężczyzny10.
    21 Wtedy to Pan sprawił, że mężczyzna pogrążył się w głębokim śnie, i gdy spał wyjął jedno z jego żeber11, a miejsce to zapełnił ciałem. 22 Po czym Pan Bóg z żebra, które wyjął z mężczyzny, zbudował niewiastę. A gdy ją przyprowadził do mężczyzny, 23 mężczyzna powiedział:
    «Ta dopiero jest kością z moich kości i ciałem z mego ciała!
    Ta będzie się zwała niewiastą, bo ta z mężczyzny została wzięta»12.
    24 Dlatego to mężczyzna opuszcza ojca swego i matkę swoją i łączy się ze swą żoną tak ściśle, że stają się jednym ciałem13.
    25 Chociaż mężczyzna i jego żona byli nadzy, nie odczuwali wobec siebie wstydu.
    pokaż całość

    +: Cronox
  •  

    1 Na początku Bóg stworzył niebo i ziemię. 2 Ziemia zaś była bezładem i pustkowiem: ciemność była nad powierzchnią bezmiaru wód, a Duch2 Boży unosił się nad wodami.
    3 Wtedy Bóg rzekł: «Niechaj się stanie światłość!» I stała się światłość. 4 Bóg widząc, że światłość jest dobra, oddzielił ją od ciemności. 5 I nazwał Bóg światłość dniem, a ciemność nazwał nocą.
    I tak upłynął wieczór i poranek - dzień pierwszy.
    6 A potem Bóg rzekł: «Niechaj powstanie sklepienie w środku wód i niechaj ono oddzieli jedne wody od drugich!» 7 Uczyniwszy to sklepienie, Bóg oddzielił wody pod sklepieniem od wód ponad sklepieniem; a gdy tak się stało, 8 Bóg nazwał to sklepienie niebem.
    I tak upłynął wieczór i poranek - dzień drugi.
    9 A potem Bóg rzekł: «Niechaj zbiorą się wody spod nieba w jedno miejsce i niech się ukaże powierzchnia sucha!» A gdy tak się stało, 10 Bóg nazwał tę suchą powierzchnię ziemią, a zbiorowisko wód nazwał morzem. Bóg widząc, że były dobre, 11 rzekł: «Niechaj ziemia wyda rośliny zielone: trawy dające nasiona, drzewa owocowe rodzące na ziemi według swego gatunku owoce, w których są nasiona». I stało się tak. 12 Ziemia wydała rośliny zielone: trawę dającą nasienie według swego gatunku i drzewa rodzące owoce, w których było nasienie według ich gatunków. A Bóg widział, że były dobre.
    13 I tak upłynął wieczór i poranek - dzień trzeci.
    14 A potem Bóg rzekł: «Niechaj powstaną ciała niebieskie, świecące na sklepieniu nieba, aby oddzielały dzień od nocy, aby wyznaczały pory roku, dni i lata; 15 aby były ciałami jaśniejącymi na sklepieniu nieba i aby świeciły nad ziemią». I stało się tak. 16 Bóg uczynił dwa duże ciała jaśniejące: większe, aby rządziło dniem, i mniejsze, aby rządziło nocą, oraz gwiazdy. 17 I umieścił je Bóg na sklepieniu nieba, aby świeciły nad ziemią; 18 aby rządziły dniem i nocą i oddzielały światłość od ciemności. A widział Bóg, że były dobre.
    19 I tak upłynął wieczór i poranek - dzień czwarty.
    20 Potem Bóg rzekł: «Niechaj się zaroją wody od roju istot żywych, a ptactwo niechaj lata nad ziemią, pod sklepieniem nieba!» 21 Tak stworzył Bóg wielkie potwory morskie i wszelkiego rodzaju pływające istoty żywe, którymi zaroiły się wody, oraz wszelkie ptactwo skrzydlate różnego rodzaju. Bóg widząc, że były dobre, 22 pobłogosławił je tymi słowami: «Bądźcie płodne i mnóżcie się, abyście zapełniały wody morskie, a ptactwo niechaj się rozmnaża na ziemi».
    23 I tak upłynął wieczór i poranek - dzień piąty.
    24 Potem Bóg rzekł: «Niechaj ziemia wyda istoty żywe różnego rodzaju: bydło, zwierzęta pełzające i dzikie zwierzęta według ich rodzajów!» I stało się tak. 25 Bóg uczynił różne rodzaje dzikich zwierząt, bydła i wszelkich zwierząt pełzających po ziemi. I widział Bóg, że były dobre. 26 3A wreszcie rzekł Bóg: «Uczyńmy człowieka na Nasz obraz, podobnego Nam. Niech panuje nad rybami morskimi, nad ptactwem powietrznym, nad bydłem, nad ziemią i nad wszystkimi zwierzętami pełzającymi po ziemi!»
    27 Stworzył więc Bóg człowieka na swój obraz,
    na obraz Boży go stworzył:
    stworzył mężczyznę i niewiastę.
    28 Po czym Bóg im błogosławił, mówiąc do nich: «Bądźcie płodni i rozmnażajcie się, abyście zaludnili ziemię i uczynili ją sobie poddaną; abyście panowali nad rybami morskimi, nad ptactwem powietrznym i nad wszystkimi zwierzętami pełzającymi po ziemi». 29 I rzekł Bóg: «Oto wam daję wszelką roślinę przynoszącą ziarno po całej ziemi i wszelkie drzewo, którego owoc ma w sobie nasienie: dla was będą one pokarmem. 30 A dla wszelkiego zwierzęcia polnego i dla wszelkiego ptactwa w powietrzu, i dla wszystkiego, co się porusza po ziemi i ma w sobie pierwiastek życia, będzie pokarmem wszelka trawa zielona». I stało się tak. 31 A Bóg widział, że wszystko, co uczynił, było bardzo dobre.
    I tak upłynął wieczór i poranek - dzień szósty.
    pokaż całość

    +: Cronox
  •  

    #aferaprezydencka

    GAWK(1) Utility Commands GAWK(1)

    NAME
    gawk - pattern scanning and processing language

    SYNOPSIS
    gawk [ POSIX or GNU style options ] -f program-file [ -- ] file ...
    gawk [ POSIX or GNU style options ] [ -- ] program-text file ...

    DESCRIPTION
    Gawk is the GNU Project's implementation of the AWK programming lan‐
    guage. It conforms to the definition of the language in the POSIX
    1003.1 Standard. This version in turn is based on the description in
    The AWK Programming Language, by Aho, Kernighan, and Weinberger. Gawk
    provides the additional features found in the current version of Brian
    Kernighan's awk and a number of GNU-specific extensions.

    The command line consists of options to gawk itself, the AWK program
    text (if not supplied via the -f or --file options), and values to be
    made available in the ARGC and ARGV pre-defined AWK variables.

    When gawk is invoked with the --profile option, it starts gathering
    profiling statistics from the execution of the program. Gawk runs more
    slowly in this mode, and automatically produces an execution profile in
    the file awkprof.out when done. See the --profile option, below.

    Gawk also has an integrated debugger. An interactive debugging session
    can be started by supplying the --debug option to the command line. In
    this mode of execution, gawk loads the AWK source code and then prompts
    for debugging commands. Gawk can only debug AWK program source pro‐
    vided with the -f option. The debugger is documented in GAWK: Effec‐
    tive AWK Programming.


    OPTION FORMAT
    Gawk options may be either traditional POSIX-style one letter options,
    or GNU-style long options. POSIX options start with a single “-”,
    while long options start with “--”. Long options are provided for both
    GNU-specific features and for POSIX-mandated features.

    Gawk-specific options are typically used in long-option form. Argu‐
    ments to long options are either joined with the option by an = sign,
    with no intervening spaces, or they may be provided in the next command
    line argument. Long options may be abbreviated, as long as the abbre‐
    viation remains unique.

    Additionally, every long option has a corresponding short option, so
    that the option's functionality may be used from within #! executable
    scripts.


    OPTIONS
    Gawk accepts the following options. Standard options are listed first,
    followed by options for gawk extensions, listed alphabetically by short
    option.

    -f program-file
    --file program-file
    Read the AWK program source from the file program-file, instead
    of from the first command line argument. Multiple -f (or
    --file) options may be used.

    -F fs
    --field-separator fs
    Use fs for the input field separator (the value of the FS prede‐
    fined variable).

    -v var=val
    --assign var=val
    Assign the value val to the variable var, before execution of
    the program begins. Such variable values are available to the
    BEGIN rule of an AWK program.

    -b
    --characters-as-bytes
    Treat all input data as single-byte characters. In other words,
    don't pay any attention to the locale information when attempt‐
    ing to process strings as multibyte characters. The --posix
    option overrides this one.

    -c
    --traditional
    Run in compatibility mode. In compatibility mode, gawk behaves
    identically to Brian Kernighan's awk; none of the GNU-specific
    extensions are recognized. See GNU EXTENSIONS, below, for more
    information.

    -C
    --copyright
    Print the short version of the GNU copyright information message
    on the standard output and exit successfully.

    -d[file]
    --dump-variables[=file]
    Print a sorted list of global variables, their types and final
    values to file. If no file is provided, gawk uses a file named
    awkvars.out in the current directory.
    Having a list of all the global variables is a good way to look
    for typographical errors in your programs. You would also use
    this option if you have a large program with a lot of functions,
    and you want to be sure that your functions don't inadvertently
    use global variables that you meant to be local. (This is a
    particularly easy mistake to make with simple variable names
    like i, j, and so on.)

    -D[file]
    --debug[=file]
    Enable debugging of AWK programs. By default, the debugger
    reads commands interactively from the terminal. The optional
    file argument specifies a file with a list of commands for the
    debugger to execute non-interactively.

    -e program-text
    --source program-text
    Use program-text as AWK program source code. This option allows
    the easy intermixing of library functions (used via the -f and
    --file options) with source code entered on the command line.
    It is intended primarily for medium to large AWK programs used
    in shell scripts.

    -E file
    --exec file
    Similar to -f, however, this is option is the last one pro‐
    cessed. This should be used with #! scripts, particularly for
    CGI applications, to avoid passing in options or source code (!)
    on the command line from a URL. This option disables command-
    line variable assignments.

    -g
    --gen-pot
    Scan and parse the AWK program, and generate a GNU .pot (Porta‐
    ble Object Template) format file on standard output with entries
    for all localizable strings in the program. The program itself
    is not executed. See the GNU gettext distribution for more
    information on .pot files.

    -h
    --help Print a relatively short summary of the available options on the
    standard output. (Per the GNU Coding Standards, these options
    cause an immediate, successful exit.)

    -i include-file
    --include include-file
    Load an awk source library. This searches for the library using
    the AWKPATH environment variable. If the initial search fails,
    another attempt will be made after appending the .awk suffix.
    The file will be loaded only once (i.e., duplicates are elimi‐
    nated), and the code does not constitute the main program
    source.

    -l lib
    --load lib
    Load a shared library lib. This searches for the library using
    the AWKLIBPATH environment variable. If the initial search
    fails, another attempt will be made after appending the default
    shared library suffix for the platform. The library initializa‐
    tion routine is expected to be named dl_load().

    -L [value]
    --lint[=value]
    Provide warnings about constructs that are dubious or non-porta‐
    ble to other AWK implementations. With an optional argument of
    fatal, lint warnings become fatal errors. This may be drastic,
    but its use will certainly encourage the development of cleaner
    AWK programs. With an optional argument of invalid, only warn‐
    ings about things that are actually invalid are issued. (This is
    not fully implemented yet.)

    -M
    --bignum
    Force arbitrary precision arithmetic on numbers. This option has
    no effect if gawk is not compiled to use the GNU MPFR and MP
    libraries.

    -n
    --non-decimal-data
    Recognize octal and hexadecimal values in input data. Use this
    option with great caution!

    -N
    --use-lc-numeric
    This forces gawk to use the locale's decimal point character
    when parsing input data. Although the POSIX standard requires
    this behavior, and gawk does so when --posix is in effect, the
    default is to follow traditional behavior and use a period as
    the decimal point, even in locales where the period is not the
    decimal point character. This option overrides the default
    behavior, without the full draconian strictness of the --posix
    option.

    -o[file]
    --pretty-print[=file]
    Output a pretty printed version of the program to file. If no
    file is provided, gawk uses a file named awkprof.out in the cur‐
    rent directory.

    -O
    --optimize
    Enable optimizations upon the internal representation of the
    program. Currently, this includes simple constant-folding, and
    tail call elimination for recursive functions. The gawk main‐
    tainer hopes to add additional optimizations over time.

    -p[prof-file]
    --profile[=prof-file]
    Start a profiling session, and send the profiling data to prof-
    file. The default is awkprof.out. The profile contains execu‐
    tion counts of each statement in the program in the left margin
    and function call counts for each user-defined function.

    -P
    --posix
    This turns on compatibility mode, with the following additional
    restrictions:

    · \x escape sequences are not recognized.

    · Only space and tab act as field separators when FS is set to a
    single space, newline does not.

    · You cannot continue lines after ? and :.

    · The synonym func for the keyword function is not recognized.

    · The operators ** and **= cannot be used in place of ^ and ^=.

    -r
    --re-interval
    Enable the use of interval expressions in regular expression
    matching (see Regular Expressions, below). Interval expressions
    were not traditionally available in the AWK language. The POSIX
    standard added them, to make awk and egrep consistent with each
    other. They are enabled by default, but this option remains for
    use with --traditional.

    -S
    --sandbox
    Runs gawk in sandbox mode, disabling the system() function,
    input redirection with getline, output redirection with print
    and printf, and loading dynamic extensions. Command execution
    (through pipelines) is also disabled. This effectively blocks a
    script from accessing local resources (except for the files
    specified on the command line).

    -t
    --lint-old
    Provide warnings about constructs that are not portable to the
    original version of UNIX awk.

    -V
    --version
    Print version information for this particular copy of gawk on
    the standard output. This is useful mainly for knowing if the
    current copy of gawk on your system is up to date with respect
    to whatever the Free Software Foundation is distributing. This
    is also useful when reporting bugs. (Per the GNU Coding Stan‐
    dards, these options cause an immediate, successful exit.)

    -- Signal the end of options. This is useful to allow further argu‐
    ments to the AWK program itself to start with a “-”. This pro‐
    vides consistency with the argument parsing convention used by
    most other POSIX programs.

    In compatibility mode, any other options are flagged as invalid, but
    are otherwise ignored. In normal operation, as long as program text
    has been supplied, unknown options are passed on to the AWK program in
    the ARGV array for processing. This is particularly useful for running
    AWK programs via the “#!” executable interpreter mechanism.

    For POSIX compatibility, the -W option may be used, followed by the
    name of a long option.


    AWK PROGRAM EXECUTION
    An AWK program consists of a sequence of pattern-action statements and
    optional function definitions.

    @include "filename"
    @load "filename"
    pattern { action statements }
    function name(parameter list) { statements }

    Gawk first reads the program source from the program-file(s) if speci‐
    fied, from arguments to --source, or from the first non-option argument
    on the command line. The -f and --source options may be used multiple
    times on the command line. Gawk reads the program text as if all the
    program-files and command line source texts had been concatenated
    together. This is useful for building libraries of AWK functions,
    without having to include them in each new AWK program that uses them.
    It also provides the ability to mix library functions with command line
    programs.

    In addition, lines beginning with @include may be used to include other
    source files into your program, making library use even easier. This
    is equivalent to using the -i option.

    Lines beginning with @load may be used to load shared libraries into
    your program. This is equivalent to using the -l option.

    The environment variable AWKPATH specifies a search path to use when
    finding source files named with the -f and -i options. If this vari‐
    able does not exist, the default path is ".:/usr/local/share/awk".
    (The actual directory may vary, depending upon how gawk was built and
    installed.) If a file name given to the -f option contains a “/” char‐
    acter, no path search is performed.

    The environment variable AWKLIBPATH specifies a search path to use when
    finding source files named with the -l option. If this variable does
    not exist, the default path is ".:/usr/local/lib/gawk". (The actual
    directory may vary, depending upon how gawk was built and installed.)

    Gawk executes AWK programs in the following order. First, all variable
    assignments specified via the -v option are performed. Next, gawk com‐
    piles the program into an internal form. Then, gawk executes the code
    in the BEGIN rule(s) (if any), and then proceeds to read each file
    named in the ARGV array (up to ARGV[ARGC]). If there are no files
    named on the command line, gawk reads the standard input.

    If a filename on the command line has the form var=val it is treated as
    a variable assignment. The variable var will be assigned the value
    val. (This happens after any BEGIN rule(s) have been run.) Command
    line variable assignment is most useful for dynamically assigning val‐
    ues to the variables AWK uses to control how input is broken into
    fields and records. It is also useful for controlling state if multi‐
    ple passes are needed over a single data file.

    If the value of a particular element of ARGV is empty (""), gawk skips
    over it.

    For each input file, if a BEGINFILE rule exists, gawk executes the
    associated code before processing the contents of the file. Similarly,
    gawk executes the code associated with ENDFILE after processing the
    file.

    For each record in the input, gawk tests to see if it matches any pat‐
    tern in the AWK program. For each pattern that the record matches,
    gawk executes the associated action. The patterns are tested in the
    order they occur in the program.

    Finally, after all the input is exhausted, gawk executes the code in
    the END rule(s) (if any).


    Command Line Directories
    According to POSIX, files named on the awk command line must be text
    files. The behavior is ``undefined'' if they are not. Most versions
    of awk treat a directory on the command line as a fatal error.

    Starting with version 4.0 of gawk, a directory on the command line pro‐
    duces a warning, but is otherwise skipped. If either of the --posix or
    --traditional options is given, then gawk reverts to treating directo‐
    ries on the command line as a fatal error.


    VARIABLES, RECORDS AND FIELDS
    AWK variables are dynamic; they come into existence when they are first
    used. Their values are either floating-point numbers or strings, or
    both, depending upon how they are used. AWK also has one dimensional
    arrays; arrays with multiple dimensions may be simulated. Gawk pro‐
    vides true arrays of arrays; see Arrays, below. Several pre-defined
    variables are set as a program runs; these are described as needed and
    summarized below.

    Records
    Normally, records are separated by newline characters. You can control
    how records are separated by assigning values to the built-in variable
    RS. If RS is any single character, that character separates records.
    Otherwise, RS is a regular expression. Text in the input that matches
    this regular expression separates the record. However, in compatibil‐
    ity mode, only the first character of its string value is used for sep‐
    arating records. If RS is set to the null string, then records are
    separated by blank lines. When RS is set to the null string, the new‐
    line character always acts as a field separator, in addition to what‐
    ever value FS may have.

    Fields
    As each input record is read, gawk splits the record into fields, using
    the value of the FS variable as the field separator. If FS is a single
    character, fields are separated by that character. If FS is the null
    string, then each individual character becomes a separate field. Oth‐
    erwise, FS is expected to be a full regular expression. In the special
    case that FS is a single space, fields are separated by runs of spaces
    and/or tabs and/or newlines. (But see the section POSIX COMPATIBILITY,
    below). NOTE: The value of IGNORECASE (see below) also affects how
    fields are split when FS is a regular expression, and how records are
    separated when RS is a regular expression.

    If the FIELDWIDTHS variable is set to a space separated list of num‐
    bers, each field is expected to have fixed width, and gawk splits up
    the record using the specified widths. The value of FS is ignored.
    Assigning a new value to FS or FPAT overrides the use of FIELDWIDTHS.

    Similarly, if the FPAT variable is set to a string representing a regu‐
    lar expression, each field is made up of text that matches that regular
    expression. In this case, the regular expression describes the fields
    themselves, instead of the text that separates the fields. Assigning a
    new value to FS or FIELDWIDTHS overrides the use of FPAT.

    Each field in the input record may be referenced by its position: $1,
    $2, and so on. $0 is the whole record. Fields need not be referenced
    by constants:

    n = 5
    print $n

    prints the fifth field in the input record.

    The variable NF is set to the total number of fields in the input
    record.

    References to non-existent fields (i.e., fields after $NF) produce the
    null-string. However, assigning to a non-existent field (e.g., $(NF+2)
    = 5) increases the value of NF, creates any intervening fields with the
    null string as their values, and causes the value of $0 to be recom‐
    puted, with the fields being separated by the value of OFS. References
    to negative numbered fields cause a fatal error. Decrementing NF
    causes the values of fields past the new value to be lost, and the
    value of $0 to be recomputed, with the fields being separated by the
    value of OFS.

    Assigning a value to an existing field causes the whole record to be
    rebuilt when $0 is referenced. Similarly, assigning a value to $0
    causes the record to be resplit, creating new values for the fields.


    Built-in Variables
    Gawk's built-in variables are:

    ARGC The number of command line arguments (does not include
    options to gawk, or the program source).

    ARGIND The index in ARGV of the current file being processed.

    ARGV Array of command line arguments. The array is indexed from
    0 to ARGC - 1. Dynamically changing the contents of ARGV
    can control the files used for data.

    BINMODE On non-POSIX systems, specifies use of “binary” mode for
    all file I/O. Numeric values of 1, 2, or 3, specify that
    input files, output files, or all files, respectively,
    should use binary I/O. String values of "r", or "w" spec‐
    ify that input files, or output files, respectively, should
    use binary I/O. String values of "rw" or "wr" specify that
    all files should use binary I/O. Any other string value is
    treated as "rw", but generates a warning message.

    CONVFMT The conversion format for numbers, "%.6g", by default.

    ENVIRON An array containing the values of the current environment.
    The array is indexed by the environment variables, each
    element being the value of that variable (e.g., ENVI‐
    RON["HOME"] might be "/home/arnold"). Changing this array
    does not affect the environment seen by programs which gawk
    spawns via redirection or the system() function.

    ERRNO If a system error occurs either doing a redirection for
    getline, during a read for getline, or during a close(),
    then ERRNO will contain a string describing the error. The
    value is subject to translation in non-English locales.

    FIELDWIDTHS A whitespace separated list of field widths. When set,
    gawk parses the input into fields of fixed width, instead
    of using the value of the FS variable as the field separa‐
    tor. See Fields, above.

    FILENAME The name of the current input file. If no files are speci‐
    fied on the command line, the value of FILENAME is “-”.
    However, FILENAME is undefined inside the BEGIN rule
    (unless set by getline).

    FNR The input record number in the current input file.

    FPAT A regular expression describing the contents of the fields
    in a record. When set, gawk parses the input into fields,
    where the fields match the regular expression, instead of
    using the value of the FS variable as the field separator.
    See Fields, above.

    FS The input field separator, a space by default. See Fields,
    above.

    FUNCTAB An array whose indices and corresponding values are the
    names of all the user-defined or extension functions in the
    program. NOTE: You may not use the delete statement with
    the FUNCTAB array.

    IGNORECASE Controls the case-sensitivity of all regular expression and
    string operations. If IGNORECASE has a non-zero value,
    then string comparisons and pattern matching in rules,
    field splitting with FS and FPAT, record separating with
    RS, regular expression matching with ~ and !~, and the gen‐
    sub(), gsub(), index(), match(), patsplit(), split(), and
    sub() built-in functions all ignore case when doing regular
    expression operations. NOTE: Array subscripting is not
    affected. However, the asort() and asorti() functions are
    affected.
    Thus, if IGNORECASE is not equal to zero, /aB/ matches all
    of the strings "ab", "aB", "Ab", and "AB". As with all AWK
    variables, the initial value of IGNORECASE is zero, so all
    regular expression and string operations are normally case-
    sensitive.

    LINT Provides dynamic control of the --lint option from within
    an AWK program. When true, gawk prints lint warnings. When
    false, it does not. When assigned the string value
    "fatal", lint warnings become fatal errors, exactly like
    --lint=fatal. Any other true value just prints warnings.

    NF The number of fields in the current input record.

    NR The total number of input records seen so far.

    OFMT The output format for numbers, "%.6g", by default.

    OFS The output field separator, a space by default.

    ORS The output record separator, by default a newline.

    PREC The working precision of arbitrary precision floating-point
    numbers, 53 by default.

    PROCINFO The elements of this array provide access to information
    about the running AWK program. On some systems, there may
    be elements in the array, "group1" through "groupn" for
    some n, which is the number of supplementary groups that
    the process has. Use the in operator to test for these
    elements. The following elements are guaranteed to be
    available:

    PROCINFO["egid"] The value of the getegid(2) system
    call.

    PROCINFO["strftime"]
    The default time format string for
    strftime().

    PROCINFO["euid"] The value of the geteuid(2) system
    call.

    PROCINFO["FS"] "FS" if field splitting with FS is in
    effect, "FPAT" if field splitting with
    FPAT is in effect, or "FIELDWIDTHS" if
    field splitting with FIELDWIDTHS is in
    effect.

    PROCINFO["identifiers"]
    A subarray, indexed by the names of all
    identifiers used in the text of the AWK
    program. The values indicate what gawk
    knows about the identifiers after it
    has finished parsing the program; they
    are not updated while the program runs.
    For each identifier, the value of the
    element is one of the following:

    "array"
    The identifier is an array.

    "extension"
    The identifier is an extension
    function loaded via @load.

    "scalar"
    The identifier is a scalar.

    "untyped"
    The identifier is untyped (could
    be used as a scalar or array,
    gawk doesn't know yet).

    "user" The identifier is a user-defined
    function.

    PROCINFO["gid"] The value of the getgid(2) system call.

    PROCINFO["pgrpid"] The process group ID of the current
    process.

    PROCINFO["pid"] The process ID of the current process.

    PROCINFO["ppid"] The parent process ID of the current
    process.

    PROCINFO["uid"] The value of the getuid(2) system call.

    PROCINFO["sorted_in"]
    If this element exists in PROCINFO,
    then its value controls the order in
    which array elements are traversed in
    for loops. Supported values are
    "@ind_str_asc", "@ind_num_asc",
    "@val_type_asc", "@val_str_asc",
    "@val_num_asc", "@ind_str_desc",
    "@ind_num_desc", "@val_type_desc",
    "@val_str_desc", "@val_num_desc", and
    "@unsorted". The value can also be the
    name of any comparison function defined
    as follows:

    function cmp_func(i1, v1, i2, v2)

    where i1 and i2 are the indices, and v1
    and v2 are the corresponding values of
    the two elements being compared. It
    should return a number less than, equal
    to, or greater than 0, depending on how
    the elements of the array are to be
    ordered.

    PROCINFO["input", "READ_TIMEOUT"]
    The timeout in milliseconds for reading
    data from input, where input is a redi‐
    rection string or a filename. A value
    of zero or less than zero means no
    timeout.

    PROCINFO["mpfr_version"]
    The version of the GNU MPFR library
    used for arbitrary precision number
    support in gawk. This entry is not
    present if MPFR support is not compiled
    into gawk.

    PROCINFO["gmp_version"]
    The version of the GNU MP library used
    for arbitrary precision number support
    in gawk. This entry is not present if
    MPFR support is not compiled into gawk.

    PROCINFO["prec_max"]
    The maximum precision supported by the
    GNU MPFR library for arbitrary preci‐
    sion floating-point numbers. This
    entry is not present if MPFR support is
    not compiled into gawk.

    PROCINFO["prec_min"]
    The minimum precision allowed by the
    GNU MPFR library for arbitrary preci‐
    sion floating-point numbers. This
    entry is not present if MPFR support is
    not compiled into gawk.

    PROCINFO["api_major"]
    The major version of the extension API.
    This entry is not present if loading
    dynamic extensions is not available.

    PROCINFO["api_minor"]
    The minor version of the extension API.
    This entry is not present if loading
    dynamic extensions is not available.

    PROCINFO["version"] the version of gawk.

    ROUNDMODE The rounding mode to use for arbitrary precision arithmetic
    on numbers, by default "N" (IEEE-754 roundTiesToEven mode).
    The accepted values are "N" or "n" for roundTiesToEven, "U"
    or "u" for roundTowardPositive, "D" or "d" for roundToward‐
    Negative, "Z" or "z" for roundTowardZero, and if your ver‐
    sion of GNU MPFR library supports it, "A" or "a" for
    roundTiesToAway.

    RS The input record separator, by default a newline.

    RT The record terminator. Gawk sets RT to the input text that
    matched the character or regular expression specified by
    RS.

    RSTART The index of the first character matched by match(); 0 if
    no match. (This implies that character indices start at
    one.)

    RLENGTH The length of the string matched by match(); -1 if no
    match.

    SUBSEP The character used to separate multiple subscripts in array
    elements, by default "\034".

    SYMTAB An array whose indices are the names of all currently
    defined global variables and arrays in the program. The
    array may be used for indirect access to read or write the
    value of a variable:

    foo = 5
    SYMTAB["foo"] = 4
    print foo # prints 4

    The isarray() function may be used to test if an element in
    SYMTAB is an array. You may not use the delete statement
    with the SYMTAB array.

    TEXTDOMAIN The text domain of the AWK program; used to find the local‐
    ized translations for the program's strings.


    Arrays
    Arrays are subscripted with an expression between square brackets ([
    and ]). If the expression is an expression list (expr, expr ...) then
    the array subscript is a string consisting of the concatenation of the
    (string) value of each expression, separated by the value of the SUBSEP
    variable. This facility is used to simulate multiply dimensioned
    arrays. For example:

    i = "A"; j = "B"; k = "C"
    x[i, j, k] = "hello, world\n"

    assigns the string "hello, world\n" to the element of the array x which
    is indexed by the string "A\034B\034C". All arrays in AWK are associa‐
    tive, i.e., indexed by string values.

    The special operator in may be used to test if an array has an index
    consisting of a particular value:

    if (val in array)
    print array[val]

    If the array has multiple subscripts, use (i, j) in array.

    The in construct may also be used in a for loop to iterate over all the
    elements of an array. However, the (i, j) in array construct only
    works in tests, not in for loops.

    An element may be deleted from an array using the delete statement.
    The delete statement may also be used to delete the entire contents of
    an array, just by specifying the array name without a subscript.

    gawk supports true multidimensional arrays. It does not require that
    such arrays be ``rectangular'' as in C or C++. For example:

    a[1] = 5
    a[2][1] = 6
    a[2][2] = 7

    NOTE: You may need to tell gawk that an array element is really a sub‐
    array in order to use it where gawk expects an array (such as in the
    second argument to split()). You can do this by creating an element in
    the subarray and then deleting it with the delete statement.


    Variable Typing And Conversion
    Variables and fields may be (floating point) numbers, or strings, or
    both. How the value of a variable is interpreted depends upon its con‐
    text. If used in a numeric expression, it will be treated as a number;
    if used as a string it will be treated as a string.

    To force a variable to be treated as a number, add 0 to it; to force it
    to be treated as a string, concatenate it with the null string.

    Uninitialized variables have the numeric value 0 and the string value
    "" (the null, or empty, string).

    When a string must be converted to a number, the conversion is accom‐
    plished using strtod(3). A number is converted to a string by using
    the value of CONVFMT as a format string for sprintf(3), with the
    numeric value of the variable as the argument. However, even though
    all numbers in AWK are floating-point, integral values are always con‐
    verted as integers. Thus, given

    CONVFMT = "%2.2f"
    a = 12
    b = a ""

    the variable b has a string value of "12" and not "12.00".

    NOTE: When operating in POSIX mode (such as with the --posix option),
    beware that locale settings may interfere with the way decimal numbers
    are treated: the decimal separator of the numbers you are feeding to
    gawk must conform to what your locale would expect, be it a comma (,)
    or a period (.).

    Gawk performs comparisons as follows: If two variables are numeric,
    they are compared numerically. If one value is numeric and the other
    has a string value that is a “numeric string,” then comparisons are
    also done numerically. Otherwise, the numeric value is converted to a
    string and a string comparison is performed. Two strings are compared,
    of course, as strings.

    Note that string constants, such as "57", are not numeric strings, they
    are string constants. The idea of “numeric string” only applies to
    fields, getline input, FILENAME, ARGV elements, ENVIRON elements and
    the elements of an array created by split() or patsplit() that are
    numeric strings. The basic idea is that user input, and only user
    input, that looks numeric, should be treated that way.


    Octal and Hexadecimal Constants
    You may use C-style octal and hexadecimal constants in your AWK program
    source code. For example, the octal value 011 is equal to decimal 9,
    and the hexadecimal value 0x11 is equal to decimal 17.

    String Constants
    String constants in AWK are sequences of characters enclosed between
    double quotes (like "value"). Within strings, certain escape sequences
    are recognized, as in C. These are:

    \\ A literal backslash.

    \a The “alert” character; usually the ASCII BEL character.

    \b Backspace.

    \f Form-feed.

    \n Newline.

    \r Carriage return.

    \t Horizontal tab.

    \v Vertical tab.

    \xhex digits
    The character represented by the string of hexadecimal digits fol‐
    lowing the \x. As in ISO C, all following hexadecimal digits are
    considered part of the escape sequence. (This feature should tell
    us something about language design by committee.) E.g., "\x1B" is
    the ASCII ESC (escape) character.

    \ddd The character represented by the 1-, 2-, or 3-digit sequence of
    octal digits. E.g., "\033" is the ASCII ESC (escape) character.

    \c The literal character c.

    The escape sequences may also be used inside constant regular expres‐
    sions (e.g., /[ \t\f\n\r\v]/ matches whitespace characters).

    In compatibility mode, the characters represented by octal and hexadec‐
    imal escape sequences are treated literally when used in regular
    expression constants. Thus, /a\52b/ is equivalent to /a\*b/.


    PATTERNS AND ACTIONS
    AWK is a line-oriented language. The pattern comes first, and then the
    action. Action statements are enclosed in { and }. Either the pattern
    may be missing, or the action may be missing, but, of course, not both.
    If the pattern is missing, the action is executed for every single
    record of input. A missing action is equivalent to

    { print }

    which prints the entire record.

    Comments begin with the # character, and continue until the end of the
    line. Blank lines may be used to separate statements. Normally, a
    statement ends with a newline, however, this is not the case for lines
    ending in a comma, {, ?, :, &&, or ||. Lines ending in do or else also
    have their statements automatically continued on the following line.
    In other cases, a line can be continued by ending it with a “\”, in
    which case the newline is ignored.

    Multiple statements may be put on one line by separating them with a
    “;”. This applies to both the statements within the action part of a
    pattern-action pair (the usual case), and to the pattern-action state‐
    ments themselves.


    Patterns
    AWK patterns may be one of the following:

    BEGIN
    END
    BEGINFILE
    ENDFILE
    /regular expression/
    relational expression
    pattern && pattern
    pattern || pattern
    pattern ? pattern : pattern
    (pattern)
    ! pattern
    pattern1, pattern2

    BEGIN and END are two special kinds of patterns which are not tested
    against the input. The action parts of all BEGIN patterns are merged
    as if all the statements had been written in a single BEGIN rule. They
    are executed before any of the input is read. Similarly, all the END
    rules are merged, and executed when all the input is exhausted (or when
    an exit statement is executed). BEGIN and END patterns cannot be com‐
    bined with other patterns in pattern expressions. BEGIN and END pat‐
    terns cannot have missing action parts.

    BEGINFILE and ENDFILE are additional special patterns whose bodies are
    executed before reading the first record of each command line input
    file and after reading the last record of each file. Inside the BEGIN‐
    FILE rule, the value of ERRNO will be the empty string if the file was
    opened successfully. Otherwise, there is some problem with the file
    and the code should use nextfile to skip it. If that is not done, gawk
    produces its usual fatal error for files that cannot be opened.

    For /regular expression/ patterns, the associated statement is executed
    for each input record that matches the regular expression. Regular
    expressions are the same as those in egrep(1), and are summarized
    below.

    A relational expression may use any of the operators defined below in
    the section on actions. These generally test whether certain fields
    match certain regular expressions.

    The &&, ||, and ! operators are logical AND, logical OR, and logical
    NOT, respectively, as in C. They do short-circuit evaluation, also as
    in C, and are used for combining more primitive pattern expressions.
    As in most languages, parentheses may be used to change the order of
    evaluation.

    The ?: operator is like the same operator in C. If the first pattern
    is true then the pattern used for testing is the second pattern, other‐
    wise it is the third. Only one of the second and third patterns is
    evaluated.

    The pattern1, pattern2 form of an expression is called a range pattern.
    It matches all input records starting with a record that matches pat‐
    tern1, and continuing until a record that matches pattern2, inclusive.
    It does not combine with any other sort of pattern expression.


    Regular Expressions
    Regular expressions are the extended kind found in egrep. They are
    composed of characters as follows:

    c Matches the non-metacharacter c.

    \c Matches the literal character c.

    . Matches any character including newline.

    ^ Matches the beginning of a string.

    $ Matches the end of a string.

    [abc...] A character list: matches any of the characters abc.... You
    may include a range of characters by separating them with a
    dash.

    [^abc...] A negated character list: matches any character except
    abc....

    r1|r2 Alternation: matches either r1 or r2.

    r1r2 Concatenation: matches r1, and then r2.

    r+ Matches one or more r's.

    r* Matches zero or more r's.

    r? Matches zero or one r's.

    (r) Grouping: matches r.

    r{n}
    r{n,}
    r{n,m} One or two numbers inside braces denote an interval expres‐
    sion. If there is one number in the braces, the preceding
    regular expression r is repeated n times. If there are two
    numbers separated by a comma, r is repeated n to m times.
    If there is one number followed by a comma, then r is
    repeated at least n times.

    \y Matches the empty string at either the beginning or the end
    of a word.

    \B Matches the empty string within a word.

    \< Matches the empty string at the beginning of a word.

    \> Matches the empty string at the end of a word.

    \s Matches any whitespace character.

    \S Matches any nonwhitespace character.

    \w Matches any word-constituent character (letter, digit, or
    underscore).

    \W Matches any character that is not word-constituent.

    \` Matches the empty string at the beginning of a buffer
    (string).

    \' Matches the empty string at the end of a buffer.

    The escape sequences that are valid in string constants (see String
    Constants) are also valid in regular expressions.

    Character classes are a feature introduced in the POSIX standard. A
    character class is a special notation for describing lists of charac‐
    ters that have a specific attribute, but where the actual characters
    themselves can vary from country to country and/or from character set
    to character set. For example, the notion of what is an alphabetic
    character differs in the USA and in France.

    A character class is only valid in a regular expression inside the
    brackets of a character list. Character classes consist of [:, a key‐
    word denoting the class, and :]. The character classes defined by the
    POSIX standard are:

    [:alnum:] Alphanumeric characters.

    [:alpha:] Alphabetic characters.

    [:blank:] Space or tab characters.

    [:cntrl:] Control characters.

    [:digit:] Numeric characters.

    [:graph:] Characters that are both printable and visible. (A space is
    printable, but not visible, while an a is both.)

    [:lower:] Lowercase alphabetic characters.

    [:print:] Printable characters (characters that are not control char‐
    acters.)

    [:punct:] Punctuation characters (characters that are not letter, dig‐
    its, control characters, or space characters).

    [:space:] Space characters (such as space, tab, and formfeed, to name
    a few).

    [:upper:] Uppercase alphabetic characters.

    [:xdigit:] Characters that are hexadecimal digits.

    For example, before the POSIX standard, to match alphanumeric charac‐
    ters, you would have had to write /[A-Za-z0-9]/. If your character set
    had other alphabetic characters in it, this would not match them, and
    if your character set collated differently from ASCII, this might not
    even match the ASCII alphanumeric characters. With the POSIX character
    classes, you can write /[[:alnum:]]/, and this matches the alphabetic
    and numeric characters in your character set, no matter what it is.

    Two additional special sequences can appear in character lists. These
    apply to non-ASCII character sets, which can have single symbols
    (called collating elements) that are represented with more than one
    character, as well as several characters that are equivalent for col‐
    lating, or sorting, purposes. (E.g., in French, a plain “e” and a
    grave-accented “`” are equivalent.)

    Collating Symbols
    A collating symbol is a multi-character collating element
    enclosed in [. and .]. For example, if ch is a collating ele‐
    ment, then [[.ch.]] is a regular expression that matches this
    collating element, while [ch] is a regular expression that
    matches either c or h.

    Equivalence Classes
    An equivalence class is a locale-specific name for a list of
    characters that are equivalent. The name is enclosed in [= and
    =]. For example, the name e might be used to represent all of
    “e,” “´,” and “`.” In this case, [[=e=]] is a regular expres‐
    sion that matches any of e, ´, or `.

    These features are very valuable in non-English speaking locales. The
    library functions that gawk uses for regular expression matching cur‐
    rently only recognize POSIX character classes; they do not recognize
    collating symbols or equivalence classes.

    The \y, \B, \<, \>, \s, \S, \w, \W, \`, and \' operators are specific
    to gawk; they are extensions based on facilities in the GNU regular
    expression libraries.

    The various command line options control how gawk interprets characters
    in regular expressions.

    No options
    In the default case, gawk provides all the facilities of POSIX
    regular expressions and the GNU regular expression operators
    described above.

    --posix
    Only POSIX regular expressions are supported, the GNU operators
    are not special. (E.g., \w matches a literal w).

    --traditional
    Traditional UNIX awk regular expressions are matched. The GNU
    operators are not special, and interval expressions are not
    available. Characters described by octal and hexadecimal escape
    sequences are treated literally, even if they represent regular
    expression metacharacters.

    --re-interval
    Allow interval expressions in regular expressions, even if
    --traditional has been provided.


    Actions
    Action statements are enclosed in braces, { and }. Action statements
    consist of the usual assignment, conditional, and looping statements
    found in most languages. The operators, control statements, and
    input/output statements available are patterned after those in C.

    Operators
    The operators in AWK, in order of decreasing precedence, are:

    (...) Grouping

    $ Field reference.

    ++ -- Increment and decrement, both prefix and postfix.

    ^ Exponentiation (** may also be used, and **= for the
    assignment operator).

    + - ! Unary plus, unary minus, and logical negation.

    * / % Multiplication, division, and modulus.

    + - Addition and subtraction.

    space String concatenation.

    | |& Piped I/O for getline, print, and printf.

    < > <= >= != ==
    The regular relational operators.

    ~ !~ Regular expression match, negated match. NOTE: Do not use
    a constant regular expression (/foo/) on the left-hand side
    of a ~ or !~. Only use one on the right-hand side. The
    expression /foo/ ~ exp has the same meaning as (($0 ~
    /foo/) ~ exp). This is usually not what you want.

    in Array membership.

    && Logical AND.

    || Logical OR.

    ?: The C conditional expression. This has the form expr1 ?
    expr2 : expr3. If expr1 is true, the value of the expres‐
    sion is expr2, otherwise it is expr3. Only one of expr2
    and expr3 is evaluated.

    = += -= *= /= %= ^=
    Assignment. Both absolute assignment (var = value) and
    operator-assignment (the other forms) are supported.


    Control Statements
    The control statements are as follows:

    if (condition) statement [ else statement ]
    while (condition) statement
    do statement while (condition)
    for (expr1; expr2; expr3) statement
    for (var in array) statement
    break
    continue
    delete array[index]
    delete array
    exit [ expression ]
    { statements }
    switch (expression) {
    case value|regex : statement
    ...
    [ default: statement ]
    }


    I/O Statements
    The input/output statements are as follows:

    close(file [, how]) Close file, pipe or co-process. The optional how
    should only be used when closing one end of a
    two-way pipe to a co-process. It must be a
    string value, either "to" or "from".

    getline Set $0 from next input record; set NF, NR, FNR,
    RT.

    getline <file Set $0 from next record of file; set NF, RT.

    getline var Set var from next input record; set NR, FNR, RT.

    getline var <file Set var from next record of file, RT.

    command | getline [var]
    Run command piping the output either into $0 or
    var, as above, and RT.

    command |& getline [var]
    Run command as a co-process piping the output
    either into $0 or var, as above, and RT. Co-pro‐
    cesses are a gawk extension. (command can also
    be a socket. See the subsection Special File
    Names, below.)

    next Stop processing the current input record. The
    next input record is read and processing starts
    over with the first pattern in the AWK program.
    Upon reaching the end of the input data, gawk
    executes any END rule(s).

    nextfile Stop processing the current input file. The next
    input record read comes from the next input file.
    FILENAME and ARGIND are updated, FNR is reset to
    1, and processing starts over with the first pat‐
    tern in the AWK program. Upon reaching the end
    of the input data, gawk executes any END rule(s).

    print Print the current record. The output record is
    terminated with the value of ORS.

    print expr-list Print expressions. Each expression is separated
    by the value of OFS. The output record is termi‐
    nated with the value of ORS.

    print expr-list >file Print expressions on file. Each expression is
    separated by the value of OFS. The output record
    is terminated with the value of ORS.

    printf fmt, expr-list Format and print. See The printf Statement,
    below.

    printf fmt, expr-list >file
    Format and print on file.

    system(cmd-line) Execute the command cmd-line, and return the exit
    status. (This may not be available on non-POSIX
    systems.)

    fflush([file]) Flush any buffers associated with the open output
    file or pipe file. If file is missing or if it
    is the null string, then flush all open output
    files and pipes.

    Additional output redirections are allowed for print and printf.

    print ... >> file
    Appends output to the file.

    print ... | command
    Writes on a pipe.

    print ... |& command
    Sends data to a co-process or socket. (See also the subsection
    Special File Names, below.)

    The getline command returns 1 on success, 0 on end of file, and -1 on
    an error. Upon an error, ERRNO is set to a string describing the prob‐
    lem.

    NOTE: Failure in opening a two-way soc
    pokaż całość

    +: Cronox
  •  

    Wykop obchodzi swoje 10 urodziny. W jaki sposób ja tworzę ten serwis? Przez ten czas opublikowałem 0 znalezisk, dodałem 75 komentarzy i 16 wpisów.
    A co Ty zrobiłeś dla Wykopu?
    #10latwykopu

    +: Cronox
  •  

    #2016 No jak tam, wykopki, szampany nasmarowane? ( ͡°( ͡° ͜ʖ( ͡° ͜ʖ ͡°)ʖ ͡°) ͡°)

  •  

    Jak na jeden miesiąc, to dużo, czy mało?

    źródło: 2015-12-28-151604_345x56_scrot.png

    +: Cronox

...to tylko najnowsze aktywności użytkownika InfuriatingCondescension

Zobacz wszystkie dodane znaleziska, komentarze i wpisy korzystając z menu powyżej.