From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28530 invoked by alias); 17 Sep 2013 19:32:54 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 28517 invoked by uid 89); 17 Sep 2013 19:32:54 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 17 Sep 2013 19:32:54 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r8HJWn2o020922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 17 Sep 2013 15:32:49 -0400 Received: from barimba (ovpn-113-63.phx2.redhat.com [10.3.113.63]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r8HJWmkq023297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 17 Sep 2013 15:32:49 -0400 From: Tom Tromey To: Doug Evans Cc: Jan Kratochvil , gdb-patches Subject: Re: [patchv3 1/5] Mostly code cleanup: Constification References: <20130915193742.GA20411@host2.jankratochvil.net> <21047.33940.998451.19883@ruffy.mtv.corp.google.com> <20130917064841.GA18677@host2.jankratochvil.net> <87txhjxr0b.fsf@fleche.redhat.com> Date: Tue, 17 Sep 2013 19:32:00 -0000 In-Reply-To: (Doug Evans's message of "Tue, 17 Sep 2013 12:24:41 -0700") Message-ID: <878uyvw8f3.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-09/txt/msg00548.txt.bz2 >>>>> "Doug" == Doug Evans writes: Doug> What's wrong with utility wrappers? In the general case they require the introduction of a new function, a new type, and marshalling and unmarshalling code. This is verbose and error prone. I suppose catch_command_errors* aren't quite so bad. Tom