From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6453 invoked by alias); 8 Feb 2002 21:41:14 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 6288 invoked from network); 8 Feb 2002 21:41:11 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 8 Feb 2002 21:41:11 -0000 Received: from cse.cygnus.com (cse.cygnus.com [205.180.230.236]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id NAA12948 for ; Fri, 8 Feb 2002 13:41:08 -0800 (PST) Received: (from kev@localhost) by cse.cygnus.com (8.11.6/8.11.6) id g18LWKX11251; Fri, 8 Feb 2002 14:32:20 -0700 Date: Fri, 08 Feb 2002 13:41:00 -0000 From: Kevin Buettner Message-Id: <1020208213220.ZM11250@localhost.localdomain> In-Reply-To: Klee Dienes "[RFA] Function return type checking" (Feb 5, 1:36am) References: X-Mailer: Z-Mail (4.0.1 13Jan97 Caldera) To: Klee Dienes , gdb-patches@sources.redhat.com Subject: Re: [RFA] Function return type checking MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-02/txt/msg00253.txt.bz2 On Feb 5, 1:36am, Klee Dienes wrote: > The following patch adds "expected return type" support to the target > function call interface. The "expected return type" is specified > using cast syntax; it is ignored if actual type information for the > function is available. If no type information is provided for a > function, the user is now required to provide an expected return type > using the cast syntax, or get an error. I've read through your explanation and the ensuing discussion to date. Though I haven't reviewed the actual patch, I think this idea makes sense and recommend that the maintainers give it serious consideration. Kevin