From owner-freebsd-standards@FreeBSD.ORG Mon Feb 18 02:00:01 2013 Return-Path: Delivered-To: freebsd-standards@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 535FD8C3 for ; Mon, 18 Feb 2013 02:00:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 0420234E for ; Mon, 18 Feb 2013 02:00:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1I200ft053942 for ; Mon, 18 Feb 2013 02:00:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1I200nI053929; Mon, 18 Feb 2013 02:00:00 GMT (envelope-from gnats) Resent-Date: Mon, 18 Feb 2013 02:00:00 GMT Resent-Message-Id: <201302180200.r1I200nI053929@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-standards@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Torsten Eichstädt Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 029FE5F5 for ; Mon, 18 Feb 2013 01:53:24 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id D7197304 for ; Mon, 18 Feb 2013 01:53:23 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.5/8.14.5) with ESMTP id r1I1rMPZ081382 for ; Mon, 18 Feb 2013 01:53:22 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.5/8.14.5/Submit) id r1I1rMxk081381; Mon, 18 Feb 2013 01:53:22 GMT (envelope-from nobody) Message-Id: <201302180153.r1I1rMxk081381@red.freebsd.org> Date: Mon, 18 Feb 2013 01:53:22 GMT From: Torsten Eichstädt To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: standards/176222: Package & Ports Is _Much_ Too Complicated. I Consider It Broken. 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, 18 Feb 2013 02:00:01 -0000 >Number: 176222 >Category: standards >Synopsis: Package & Ports Is _Much_ Too Complicated. I Consider It Broken. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-standards >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Feb 18 02:00:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Torsten Eichstädt >Release: 9.1 >Organization: >Environment: FreeBSD paul-lifebook 9.1-RELEASE FreeBSD 9.1-RELEASE #2: Tue Nov 27 03:45:16 UTC 2012 root@darkstar:/usr/obj/pcbsd-build90/fbsd-source/9.1/sys/GENERIC amd64 >Description: The implementations of Packages & Ports are 80ies spirited and UNIXish. In this case, this means: bad. Bad wrt robustness (they can easily render your system inconsistent) and user friendliness. It's documentation is incomplete. The tools do not have reasonable default settings, e.g. to install dependencies (often: "-R") should be default; it isn't. To begin installing the 1st dep only after all other packages/ports are downloaded, should be default behaviour; it isn't. To automagically use the "nearest" mirror(s) should be default; it isn't. To try other mirrors when a package/port could not be found should be default; it isn't. De-installing a package that was installed as a dependency and is not needed anymore should be default; it isn't. Etc. pp. Who wants to remember all those commandline switches, plus they are different from tool to tool? The options should be there for non-default usage. The tools give error messages w/o telling how to fix the error occured. A novice user will run into trouble, even when s/he reads a plethora of books on BSD. Even an experienced user can (and many will) shoot herself in the foot now and then. You can exchange "portinstall" w/ other tools below; they all have the these bugs. >How-To-Repeat: On a fresh, default (just select KDE desktop and _change nothing_ (important, else the installation fails :)) PC-BSD system with ports tree initialized w/ System Manager GUI, try to install the FreeBSD docs: [1st bug: I must not forget to RTFM 1st, although simply installing a package is much easier on e.g. Linux, Solaris, Windows or Mac, and it shold be easy on BSD, too] [2nd bug: It takes hours to find out how to get a list of packages & ports and their description] [3rd bug:] # portinstall -v -PP -R freebsd-doc-en ** No such package or port: freebsd-doc-en [but ommiting the category was ok for other pkgs...] # portinstall -v -PP misc/freebsd-doc-en [...] ---> ** Install tasks 1: 0 done, 0 ignored, 0 skipped and 1 failed ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) ! misc/freebsd-doc-en (package not found) [4th bug: portinstall tried the master site several times, not the mirrors. I have "fastest_sites" installed (and conf'd as suggested). What is it good for? And I can find the pkgs on the web interface and additionally, read the docs online. So I think, ok, maybe there's a newer version not packaged yet, so I try:] # portinstall -v -P misc/freebsd-doc-en [...] ===> Cleaning for zh-arphicttf-2.11_2 You may use the following options: WITH_GS - if you want Ghostscript support WITHOUT_X11 - if you DON'T want X Window support [bug #5: Yes, I'd like to. But HOW??? Is it too much to write it there??? Or better: write to a list that is shown at the end, after the whole installation.] [...] I tried to use KPorts (the KDE3 version, because they write the new version is not as good yet). No way. It starts with: "Failed to update or read the FTPINDEX. You will not be able to use Packages." Details: "COMMAND RUN: uma -v 85335 fetch ftpindex RETURN VALUE: 16 LOG: fetch: ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-release/INDEX: File unavailable (e.g., file not found, no access) ERROR(16): Fetching remote INDEX failed." It does not remember my change of the ftp site in it's config GUI to use the german or swedish mirror. Many many other bugs, too, so I better use command line tools. >Fix: Mark all that stuff for throwing in the pre-1990-trashbin. Port the new Solaris packaging system, or better: adopt ideas from it. There are always things to do better, but I've never had such problems on Linux, OpenSolaris or Indiana. E.g. updates to precompiled packages could contain binary diffs plus some logic to update conf files and dependencies (In the simplest case a wrapper to the app that shows some description what to do manually), saving bandwidth and making it more or less easy to rollback on a system w/o fs snapshots and do not rely on snapshots (blindly rollback the fs can be desastrous 'cause you rollback data, too). In many cases it would be possible to deliver binary diffs that relate to compile-time options for packages. The flat structuring is insufficient. Many packages belong to more than one category (it looks like the so-called "structure" at the top of the GNU-info docs ;). E.g. category "lang": The usual meaning of "language" is "natural human language" . BTW, a reasonable handling for intl'n is non-existent, I have the option to install all languages or nothing. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-standards@FreeBSD.ORG Mon Feb 18 02:57:53 2013 Return-Path: Delivered-To: freebsd-standards@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3A4341AE; Mon, 18 Feb 2013 02:57:53 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id EE6EF738; Mon, 18 Feb 2013 02:57:52 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1I2vqD8065815; Mon, 18 Feb 2013 02:57:52 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1I2vqtZ065811; Mon, 18 Feb 2013 02:57:52 GMT (envelope-from eadler) Date: Mon, 18 Feb 2013 02:57:52 GMT Message-Id: <201302180257.r1I2vqtZ065811@freefall.freebsd.org> To: torsten.eichstaedt@web.de, eadler@FreeBSD.org, freebsd-standards@FreeBSD.org From: eadler@FreeBSD.org Subject: Re: standards/176222: Package & Ports Is _Much_ Too Complicated. I Consider It Broken. 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, 18 Feb 2013 02:57:53 -0000 Synopsis: Package & Ports Is _Much_ Too Complicated. I Consider It Broken. State-Changed-From-To: open->closed State-Changed-By: eadler State-Changed-When: Mon Feb 18 02:57:52 UTC 2013 State-Changed-Why: I've sent a private mail explaining that these sorts of discussions are ill-suited to a bug tracker, and I've asked that the OP please follow up to the ports@ mailing list to start the discussion http://www.freebsd.org/cgi/query-pr.cgi?pr=176222 From owner-freebsd-standards@FreeBSD.ORG Mon Feb 18 02:58:48 2013 Return-Path: Delivered-To: freebsd-standards@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9381A1E2; Mon, 18 Feb 2013 02:58:48 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 6C47973F; Mon, 18 Feb 2013 02:58:48 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1I2wmj8065899; Mon, 18 Feb 2013 02:58:48 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1I2wm43065895; Mon, 18 Feb 2013 02:58:48 GMT (envelope-from eadler) Date: Mon, 18 Feb 2013 02:58:48 GMT Message-Id: <201302180258.r1I2wm43065895@freefall.freebsd.org> To: eadler@FreeBSD.org, freebsd-standards@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org From: eadler@FreeBSD.org Subject: Re: ports/176222: Package & Ports Is _Much_ Too Complicated. I Consider It Broken. 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, 18 Feb 2013 02:58:48 -0000 Synopsis: Package & Ports Is _Much_ Too Complicated. I Consider It Broken. Responsible-Changed-From-To: freebsd-standards->freebsd-ports-bugs Responsible-Changed-By: eadler Responsible-Changed-When: Mon Feb 18 02:58:26 UTC 2013 Responsible-Changed-Why: over to appropriate list http://www.freebsd.org/cgi/query-pr.cgi?pr=176222 From owner-freebsd-standards@FreeBSD.ORG Mon Feb 18 11:06:52 2013 Return-Path: Delivered-To: freebsd-standards@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F274023B for ; Mon, 18 Feb 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]) by mx1.freebsd.org (Postfix) with ESMTP id E405CE3A for ; Mon, 18 Feb 2013 11:06:52 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1IB6qU6061702 for ; Mon, 18 Feb 2013 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1IB6qeB061700 for freebsd-standards@FreeBSD.org; Mon, 18 Feb 2013 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 18 Feb 2013 11:06:52 GMT Message-Id: <201302181106.r1IB6qeB061700@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, 18 Feb 2013 11:06:53 -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/175711 standards When the server has more than 3 days, rising interrupt o 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 o 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/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 p stand/107561 standards [libc] [patch] [request] Missing SUS function tcgetsid o stand/100017 standards [Patch] Add fuser(1) functionality to fstat(1) a stand/86484 standards [patch] mkfifo(1) uses wrong permissions o stand/82654 standards C99 long double math functions are missing 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 40 problems total. From owner-freebsd-standards@FreeBSD.ORG Fri Feb 22 09:55:05 2013 Return-Path: Delivered-To: freebsd-standards@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4EF366E7; Fri, 22 Feb 2013 09:55:05 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) by mx1.freebsd.org (Postfix) with ESMTP id 244C6288; Fri, 22 Feb 2013 09:55:04 +0000 (UTC) Received: from [192.168.0.2] (cpc10-cmbg15-2-0-cust123.5-4.cable.virginmedia.com [86.30.246.124]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r1M9ss8r062937 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 22 Feb 2013 09:54:57 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: standards/175811: libstdc++ needs complex support in order use C99 From: David Chisnall In-Reply-To: <510F306A.6090009@missouri.edu> Date: Fri, 22 Feb 2013 09:54:48 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201302040328.r143SUd3039504@freefall.freebsd.org> <510F306A.6090009@missouri.edu> To: Stephen Montgomery-Smith X-Mailer: Apple Mail (2.1499) Cc: pfg@FreeBSD.org, freebsd-standards@FreeBSD.org, freebsd-numerics@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: Fri, 22 Feb 2013 09:55:05 -0000 On 4 Feb 2013, at 03:52, Stephen Montgomery-Smith = wrote: > We do really seem to have a lot of working code right now. And the = main > barrier to commitment seems to be style issues. >=20 > For example, I have code at http://people.freebsd.org/~stephen/ for = the > complex arctrig functions. And Bruce has clog available. And > presumably he has logl and atanl also available. >=20 > The last I heard about my code is Bruce asking for some style changes. > However I really don't think I will have time to work on it until at > least the summer. And to be honest, style just isn't my thing. >=20 > I propose (a) that someone else takes over my code (and maybe Bruce's > code) and make the style changes, or (b) that we get a little less = fussy > about getting it all just so right and start committing stuff. >=20 > Let me add that the code we have is already far superior than anything > in Linux or NetBSD, who clearly didn't worry about huge numerical = errors > in many edge cases. Come on guys, let's start strutting our stuff. >=20 > Let's commit what we have, even if it isn't perfect. Yes, please can this happen? We are currently on 31 test failures in = the libc++ test suite on -HEAD, of which at least 18 are due to linker = failures trying to find missing libm functions. We are very close to = having a complete C++11 implementation, yet we are held up by the lack = of C99 support, and we are held up there by style nits? On behalf of core, please can we commit the existing code and worry = about the style later? Given the expertise required to work on the libm = functions, most of the people who are able to hack on the code have = already read it and so concerns about consistency readability are = somewhat misplaced. David From owner-freebsd-standards@FreeBSD.ORG Fri Feb 22 16:08:13 2013 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 97903632 for ; Fri, 22 Feb 2013 16:08:13 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from nm25-vm3.bullet.mail.gq1.yahoo.com (nm25-vm3.bullet.mail.gq1.yahoo.com [98.136.217.114]) by mx1.freebsd.org (Postfix) with ESMTP id 5581499D for ; Fri, 22 Feb 2013 16:08:13 +0000 (UTC) Received: from [98.137.12.188] by nm25.bullet.mail.gq1.yahoo.com with NNFMP; 22 Feb 2013 16:01:14 -0000 Received: from [98.136.185.45] by tm9.bullet.mail.gq1.yahoo.com with NNFMP; 22 Feb 2013 16:01:14 -0000 Received: from [127.0.0.1] by smtp106.mail.gq1.yahoo.com with NNFMP; 22 Feb 2013 16:01:14 -0000 X-Yahoo-Newman-Id: 831789.33090.bm@smtp106.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: T2WMbKsVM1kRSgufr8tM1GkE6zcZGGL_q1jGdQ0TIfJPiQ. MFSwAK5ek8kL83YZDMH81kYMCavm0ChWCQQiJP.syL06vz.lJ_2xboguop83 7sGPmkfTNyZiRBwY.Ic6CCqgvtMnbxNrNJpyrJP8ZL.B4Zi7Y3lyhr_XHYGl GJAryX3r0.vB_57f4RAuF7zjmmxuv8ADCpZ13R6FggpN5EXec569IkDF3VcA 7KQwHgBO5NkRAPo411RKYSfellwvfjTjwcDeyqwcA5ypIkGpNR4nipoFZrHd D4pWxJSI7PG7Rk.MeHEQVVGENB7oACpmbZkfRApYGSJOZbscGg_BH8DDIWqe Psr5MuYZnVvCMoPX58nX3VGaRLmXHCRt9gvCN1rUI3zI0r9jByGlHFQiG0C4 mmp07oUSm6U1iGoS_I2iGlT4GJZ8kbWoO8GyW_gfr9Atxg8GgSFxONH3DlrO jPdNXPOXFFHreHp6M1tJ50RLr8pA6FItsuJ9KRS5APR.aIstsv1.XLji5yPR WcLNO9lmLQrvppxKRKy0bPiUx9xSWhZz_Ur54.uEvRQcLUq4- X-Yahoo-SMTP: xcjD0guswBAZaPPIbxpWwLcp9Unf Received: from [192.168.10.102] (pfg@200.118.157.7 with plain) by smtp106.mail.gq1.yahoo.com with SMTP; 22 Feb 2013 08:01:14 -0800 PST Message-ID: <5127964D.5080005@FreeBSD.org> Date: Fri, 22 Feb 2013 11:01:17 -0500 From: Pedro Giffuni User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130201 Thunderbird/17.0.2 MIME-Version: 1.0 To: David Chisnall Subject: Re: standards/175811: libstdc++ needs complex support in order use C99 References: <201302040328.r143SUd3039504@freefall.freebsd.org> <510F306A.6090009@missouri.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Stephen Montgomery-Smith , freebsd-numerics@FreeBSD.org, 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: Fri, 22 Feb 2013 16:08:13 -0000 Hello guys; On 02/22/2013 04:54, David Chisnall wrote: > On 4 Feb 2013, at 03:52, Stephen Montgomery-Smith wrote: > >> We do really seem to have a lot of working code right now. And the main >> barrier to commitment seems to be style issues. >> >> For example, I have code at http://people.freebsd.org/~stephen/ for the >> complex arctrig functions. And Bruce has clog available. And >> presumably he has logl and atanl also available. >> >> The last I heard about my code is Bruce asking for some style changes. >> However I really don't think I will have time to work on it until at >> least the summer. And to be honest, style just isn't my thing. >> >> I propose (a) that someone else takes over my code (and maybe Bruce's >> code) and make the style changes, or (b) that we get a little less fussy >> about getting it all just so right and start committing stuff. >> >> Let me add that the code we have is already far superior than anything >> in Linux or NetBSD, who clearly didn't worry about huge numerical errors >> in many edge cases. Come on guys, let's start strutting our stuff. >> >> Let's commit what we have, even if it isn't perfect. > Yes, please can this happen? We are currently on 31 test failures in the libc++ test suite on -HEAD, of which at least 18 are due to linker failures trying to find missing libm functions. We are very close to having a complete C++11 implementation, yet we are held up by the lack of C99 support, and we are held up there by style nits? > > On behalf of core, please can we commit the existing code and worry about the style later? Given the expertise required to work on the libm functions, most of the people who are able to hack on the code have already read it and so concerns about consistency readability are somewhat misplaced. The problem is not really lack of committers I guess ;). Can the numeric guys just put a patch together for testing? Pedro.