From owner-freebsd-standards@FreeBSD.ORG Mon Sep 30 11:06:52 2013 Return-Path: Delivered-To: freebsd-standards@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7BEE8EA3 for ; Mon, 30 Sep 2013 11:06:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 695972C02 for ; Mon, 30 Sep 2013 11:06:52 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r8UB6qbE053616 for ; Mon, 30 Sep 2013 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r8UB6pqw053614 for freebsd-standards@FreeBSD.org; Mon, 30 Sep 2013 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 30 Sep 2013 11:06:51 GMT Message-Id: <201309301106.r8UB6pqw053614@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-standards@FreeBSD.org Subject: Current problem reports assigned to freebsd-standards@FreeBSD.org X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Sep 2013 11:06:52 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o stand/181541 standards DRQVQzLUL8 o stand/179248 standards A return value of telldir(3) only seekable for once o stand/177742 standards conflict of dd's bs= option with use of conv=sparse o stand/176683 standards catman pages shall be stored in /var (/usr/local/var,/ o stand/176412 standards newfs writes by default, compare to bsdlabel/disklabel o stand/175711 standards When the server has more than 3 days, rising interrupt p stand/175453 standards Catching C++ std::bad_cast doesn't work in FreeBSD 9.1 o stand/174938 standards Problem statement: iSCSI target failure o stand/173421 standards [libc] [patch] strptime() accepts formats that should o stand/173087 standards pax(1) does not support the pax interchange format o stand/172805 standards Fix catopen(3)'s EINVAL usage and document EFTYPE o stand/172276 standards POSIX: {get,set}groups gidsetsize is u_int not int o stand/172215 standards localeconv() grouping appears not to match POSIX o stand/170403 standards wrong ntohs expression type tickling clang o stand/169697 standards syslogd(8) is not BOM aware o stand/166349 standards Support the assignment-allocation character for fscanf p stand/164787 standards dirfd() function not available when _POSIX_C_SOURCE is o kern/164674 standards [patch] [libc] vfprintf/vfwprintf return error (EOF) o o stand/162434 standards getaddrinfo: addrinfo.ai_family is an address family, o stand/150093 standards C++ std::locale support is broken o stand/130067 standards Wrong numeric limits in system headers? o stand/125751 standards man 3 pthread_getschedparam section ERRORS incomplete o stand/124860 standards flockfile(3) doesn't work when the memory has been exh o stand/121921 standards [patch] Add leap second support to at(1), atrun(8) o stand/116477 standards rm(1): rm behaves unexpectedly when using -r and relat o bin/116413 standards incorrect getconf(1) handling of unsigned constants gi o stand/116081 standards make does not work with the directive sinclude a stand/86484 standards [patch] mkfifo(1) uses wrong permissions o stand/81287 standards [patch] fingerd(8) might send a line not ending in CRL a stand/80293 standards sysconf() does not support well-defined unistd values o stand/79056 standards [feature request] [atch] regex(3) regression tests o stand/70813 standards [patch] ls(1) not Posix compliant o stand/66357 standards make POSIX conformance problem ('sh -e' & '+' command- s kern/64875 standards [libc] [patch] [request] add a system call: fdatasync( o stand/56476 standards [patch] cd9660 unicode support simple hack o stand/54410 standards one-true-awk not POSIX compliant (no extended REs) o stand/46119 standards Priority problems for SCHED_OTHER using pthreads o stand/44365 standards [headers] [patch] [request] introduce ulong and unchar a stand/41576 standards ln(1): replacing old dir-symlinks a docs/26003 standards getgroups(2) lists NGROUPS_MAX but not syslimits.h s stand/24590 standards timezone function not compatible witn Single Unix Spec o stand/21519 standards sys/dir.h should be deprecated some more s bin/14925 standards getsubopt isn't poisonous enough 43 problems total. From owner-freebsd-standards@FreeBSD.ORG Tue Oct 1 20:02:21 2013 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8173C507; Tue, 1 Oct 2013 20:02:21 +0000 (UTC) (envelope-from crees@physics.org) Received: from mk-outboundfilter-2.mail.uk.tiscali.com (mk-outboundfilter-2.mail.uk.tiscali.com [212.74.114.38]) by mx1.freebsd.org (Postfix) with ESMTP id C595D25B0; Tue, 1 Oct 2013 20:02:20 +0000 (UTC) X-Trace: 20075414/mk-outboundfilter-2.mail.uk.tiscali.com/PIPEX/$ON_NET_AUTH_ACCEPTED/Talk_Talk_Customer/2.102.106.185/None/crees@physics.org X-SBRS: None X-RemoteIP: 2.102.106.185 X-IP-MAIL-FROM: crees@physics.org X-SMTP-AUTH: bayofrum@uwclub.net X-MUA: Mozilla/5.0 (Windows NT 6.0; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AosHANooS1ICZmq5/2dsb2JhbABagwdGA75MgnsKgScXdIIlAQEFOB4iARALDgoJFg8JAwIBAgEnHgYNAQcBAYgGvU2PUQcug3QDnh4Ui0eDJTs X-IPAS-Result: AosHANooS1ICZmq5/2dsb2JhbABagwdGA75MgnsKgScXdIIlAQEFOB4iARALDgoJFg8JAwIBAgEnHgYNAQcBAYgGvU2PUQcug3QDnh4Ui0eDJTs X-IronPort-AV: E=Sophos;i="4.90,1015,1371078000"; d="scan'208";a="20075414" X-IP-Direction: OUT Received: from host-2-102-106-185.as13285.net (HELO pegasus.bayofrum.net) ([2.102.106.185]) by smtp.pipex.tiscali.co.uk with ESMTP; 01 Oct 2013 21:01:10 +0100 Received: from [192.168.1.148] (athene.bayofrum.net [192.168.1.148]) by pegasus.bayofrum.net (Postfix) with ESMTPSA id 918B2320F2; Tue, 1 Oct 2013 21:01:08 +0100 (BST) Message-ID: <524B2A27.7050908@physics.org> Date: Tue, 01 Oct 2013 21:01:43 +0100 From: Chris Rees User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Damian Weber Subject: Re: bug with special bracket expressions in regular expressions References: <5224A693.3000904@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-bayofrum-MailScanner-Information: Please contact the ISP for more information X-bayofrum-MailScanner-ID: 918B2320F2.A6F9C X-bayofrum-MailScanner: Found to be clean X-bayofrum-MailScanner-From: crees@physics.org X-Spam-Status: No Cc: FreeBSD Current , freebsd-standards@FreeBSD.org, Andriy Gapon X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Oct 2013 20:02:21 -0000 On 02/09/2013 16:09, Damian Weber wrote: > > On Mon, 2 Sep 2013, Andriy Gapon wrote: > >> re_format(7) says: >> There are two special cases? of bracket expressions: the bracket expres? >> sions ?[[:<:]]? and ?[[:>:]]? match the null string at the beginning and >> end of a word respectively. A word is defined as a sequence of word >> characters which is neither preceded nor followed by word characters. A >> word character is an alnum character (as defined by ctype(3)) or an >> underscore. This is an extension, compatible with but not specified by >> IEEE Std 1003.2 (?POSIX.2?), and should be used with caution in software >> intended to be portable to other systems. >> >> However I observe the following: >> $ echo "cd0 cd1 xx" | sed 's/cd[0-9][^ ]* *//g' >> xx >> $ echo "cd0 cd1 xx" | sed 's/[[:<:]]cd[0-9][^ ]* *//g' >> cd1 xx >> >> In my opinion '[[:<:]]' should not affect how the pattern is matched in this case. >> >> Any thoughts, suggestions? > there are two simpler expressions, whose difference I don't understand either > (tested on 8.4-PRERELEASE) > > $ echo "cd0 cd1 xx" | sed 's/cd[0-9] //g' > xx > $ echo "cd0 cd1 xx" | sed 's/[[:<:]]cd[0-9] //g' > cd1 xx Well, I agree with your analysis, and I think it's certainly a bug. Do you think that the BUGS line in regex(3) should perhaps be extended to "never works properly"?: """ Word-boundary matching does not work properly in multibyte locales. """ [[:<:]] can be replaced by \b in a pcre, which works perfectly fine (of course) echo "this word word should be deleted" | perl -pe 's,\bword ,,g' this should be deleted Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-standards@FreeBSD.ORG Sat Oct 5 00:10:00 2013 Return-Path: Delivered-To: freebsd-standards@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 63123385 for ; Sat, 5 Oct 2013 00:10:00 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 36B952EBB for ; Sat, 5 Oct 2013 00:10:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r950A09A044258 for ; Sat, 5 Oct 2013 00:10:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r950A0xg044254; Sat, 5 Oct 2013 00:10:00 GMT (envelope-from gnats) Date: Sat, 5 Oct 2013 00:10:00 GMT Message-Id: <201310050010.r950A0xg044254@freefall.freebsd.org> To: Simon From: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: ports/182657: [patch] lang/gcc48: expose c99 math in 'std' namespace In-Reply-To: Your message of Sat, 5 Oct 2013 00:09:48 GMT <201310050009.r9509mPW064394@oldred.freebsd.org> X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Oct 2013 00:10:00 -0000 Thank you very much for your problem report. It has the internal identification `ports/182657'. The individual assigned to look at your report is: freebsd-ports-bugs. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=182657 >Category: ports >Responsible: freebsd-ports-bugs >Synopsis: [patch] lang/gcc48: expose c99 math in 'std' namespace >Arrival-Date: Sat Oct 05 00:10:00 UTC 2013