From owner-sc22wg5@open-std.org  Thu Jul 17 02:17:10 2008
Return-Path: <owner-sc22wg5@open-std.org>
X-Original-To: sc22wg5-dom6
Delivered-To: sc22wg5-dom6@open-std.org
Received: by open-std.org (Postfix, from userid 521)
	id B16FADA74E; Thu, 17 Jul 2008 02:17:10 +0200 (CET DST)
X-Original-To: sc22wg5@open-std.org
Delivered-To: sc22wg5@open-std.org
Received: from mail.edogawa-u.ac.jp (mail.edogawa-u.ac.jp [210.235.130.12])
	by open-std.org (Postfix) with ESMTP id 28B1123A4A
	for <sc22wg5@open-std.org>; Thu, 17 Jul 2008 02:17:00 +0200 (CET DST)
Received: from mail.edogawa-u.ac.jp (localhost [127.0.0.1])
	by mail.edogawa-u.ac.jp with SMTP id m6H0Gvg8012649
	for <sc22wg5@open-std.org>; Thu, 17 Jul 2008 09:16:57 +0900 (JST)
Received: (qmail 12647 invoked by uid 0); 17 Jul 2008 09:16:57 +0900
Received: from localhost (HELO mail.edogawa-u.ac.jp) (127.0.0.1)
  by localhost with SMTP; 17 Jul 2008 09:16:57 +0900
Received: from TAKATA-N9.edogawa-u.ac.jp (vpn144004.edogawa-u.ac.jp [210.235.144.4])
	by mail.edogawa-u.ac.jp with ESMTP id m6H0GpUX012444;
	Thu, 17 Jul 2008 09:16:56 +0900 (JST)
Message-Id: <5.1.1.11.2.20080717090035.05ec9008@mail.edogawa-u.ac.jp>
X-Sender: takata@mail.edogawa-u.ac.jp
X-Mailer: QUALCOMM Windows Eudora Version 5.1J Jr5-rev2
Date: Thu, 17 Jul 2008 09:16:47 +0900
To: longb@cray.com
From: TAKATA Masayuki <takata@edogawa-u.ac.jp>
Subject: Re: [2205jp 1510] (SC22WG5.3588) (j3.2006) OPTIONAL arguments
  and C interop
Cc: sc22wg5@open-std.org
In-Reply-To: <20080716203724.5E5B0D9F76@open-std.org>
References: <OF0633F6D6.B3ADBEAE-ON85257488.006601F0-85257488.006AB77E@ca.ibm.com>
 <OF0633F6D6.B3ADBEAE-ON85257488.006601F0-85257488.006AB77E@ca.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

Bill,

Why didn't you couple each hidden flag with the corresponding optional argument 
to form a struct?

Makki

At 08/07/16 15:36 -0500, Bill Long wrote:
> 2) The idea of specifying extra hidden arguments for any reason is 
> abhorrent.  You end up with a situation where the Fortran interface and 
> the C prototype do not correspond even in the number of arguments.  
> Further, if you have an interface with many optional arguments, 
> intermixed with hundreds of nonoptional arguments, keeping track of 
> which flags go with which arguments (which the C user has to do 
> manually) becomes unmaintainable.  Hidden arguments are fine as long as 
> they are always hidden.  When you have to expose them, they are a bad idea.

-- 
Takata, Masayuki: Professor
Edogawa University, Nagareyama, Chiba 270-0198 Japan
phone:+81-4-7152-0661ext546   fax:+81-4-7154-2490
http://www.edogawa-u.ac.jp/~takata/


