From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) by sourceware.org (Postfix) with ESMTPS id 7E3E4385DC33 for ; Sun, 23 May 2021 15:35:22 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 7E3E4385DC33 Received: by mail-io1-xd2a.google.com with SMTP id e17so12720217iol.7 for ; Sun, 23 May 2021 08:35:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:openpgp:in-reply-to:references:from:mime-version :date:message-id:subject:to:cc; bh=vIEdwmu+f1hXP6cTcn1dbBWMgAvDs3HyGd3JSekmmlQ=; b=RG57ASKtrQgo+gqoi9K2edkPacgh7jYFS6dwmHIoQnZPq4jFyoDvP5gJRSEkReQ/OO xB1m6eO6x7oqdr8QNqa4f7o8uKCTPA/MJNMZo4jMIj71FpkzlxgvOzAwm0P7wwQYoH4a y33Mog3FwOXdzfvrwygdBqO+JmhSh4U3pDW+iwmlEX6oUJPXWT/WXgJe4MWaoeCuKJXA F3aXzib8L76rLp7N7fLXg/cgAaOmw/7p+Bgp+XYaHyMFi4QegxsmA7ClcaiCQ6CVfakN 78cH1X1+fQMeGo1l+KoOmkeuvRWtTqRSb0d5Xu2KIJMGaB7kHH5mHvbEHrzQS18snvRs rdZA== X-Gm-Message-State: AOAM531PMs0+TyV1/Q5uEh/t2FCtXySAUnXbIN4dWrITN9FbIj8WUOkw /rjqcjYMPTbkKNcwEH4OhC5ouemJXlyWraM4xlcT+mtcfig= X-Google-Smtp-Source: ABdhPJwB5X1KRjhBhrW4FyUfntPPd9fkG6ZF9eVkR9OKZNYsDTNNos1MPD2keRvqgcHIRsX6+HeCCr18cpNllt/XygY= X-Received: by 2002:a05:6638:287:: with SMTP id c7mr18077225jaq.137.1621784122110; Sun, 23 May 2021 08:35:22 -0700 (PDT) Received: from 717284730244 named unknown by gmailapi.google.com with HTTPREST; Sun, 23 May 2021 10:35:21 -0500 Openpgp: id=FB96FDADB4F197A1 In-Reply-To: <20210523151237.GB18845@tuxteam.de> References: <20210523140555.GA18845@tuxteam.de> <20210523151237.GB18845@tuxteam.de> From: Peng Yu MIME-Version: 1.0 Date: Sun, 23 May 2021 10:35:21 -0500 Message-ID: Subject: Re: http://manpagez.com/man/3/regex/ To: tomas@tuxteam.de Cc: libc-help@sourceware.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 May 2021 15:35:24 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I've already read it before I sent the first email. My conclusion is that glibc regex doesn't support REG_ENHANCED. But the manual could be outdated. So I want to confirm if it is the case. Again, I am not asking REG_EXTENDED. I am asking REG_ENHANCED. If you don't want to asnwer my question specifically, then just don't asnwer. Please don't answer something that I did not ask. It is just a distraction. - -- Regards, Peng On 2021-05-23 at 15:12, tomas@tuxteam.de wrote: > On Sun, May 23, 2021 at 09:43:01AM -0500, Peng Yu wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA512 > > > > That was not my question. I am asking whether libc regex support > > REG_ENHANCED or not. > > Sigh. It's all in the ref I gave you. It has to support > REG_EXTENDED because it supports POSIX. You have to compile > it with POSIX support. > > Please, read at least the refs given to you if someone does > the work of looking things up. > > Cheers > - t -----BEGIN PGP SIGNATURE----- Version: FlowCrypt Email Encryption 8.0.7 Comment: Seamlessly send and receive encrypted email wnUEARYKAAYFAmCqdjgAIQkQ+5b9rbTxl6EWIQTEGysjBAeh5ljon4/7lv2t tPGXoZGfAQCvgl5C/WT+KQcRALWlvq8xRHSn6coD/6yyT66pbfgLyQEArNBA IjijHcRRmjtWun/yq8R3Av1h2f/GhsPxlgR+vQg= =OCCj -----END PGP SIGNATURE-----