From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7453 invoked by alias); 9 Jan 2013 17:23:17 -0000 Received: (qmail 7433 invoked by uid 22791); 9 Jan 2013 17:23:15 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp22.services.sfr.fr (HELO smtp22.services.sfr.fr) (93.17.128.13) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 09 Jan 2013 17:23:06 +0000 Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2217.sfr.fr (SMTP Server) with ESMTP id 029A7700036C; Wed, 9 Jan 2013 18:23:05 +0100 (CET) Received: from [192.168.1.58] (160.183.72.86.rev.sfr.net [86.72.183.160]) by msfrf2217.sfr.fr (SMTP Server) with ESMTP id 86985700036B; Wed, 9 Jan 2013 18:23:04 +0100 (CET) X-SFR-UUID: 20130109172304553.86985700036B@msfrf2217.sfr.fr Message-ID: <50EDA772.5030704@sfr.fr> Date: Wed, 09 Jan 2013 17:23:00 -0000 From: Mikael Morin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121222 Thunderbird/10.0.11 MIME-Version: 1.0 To: Tobias Burnus CC: Janne Blomqvist , gcc patches , gfortran Subject: Re: [Patch, Fortran] PR55758 - Non-C_Bool handling with BIND(C) References: <50DCCC29.6010206@net-b.de> <50E01A7C.2090106@net-b.de> <50E9ABC7.4040705@net-b.de> <50ED9949.8010607@net-b.de> In-Reply-To: <50ED9949.8010607@net-b.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2013-01/txt/msg00499.txt.bz2 Le 09/01/2013 17:22, Tobias Burnus a écrit : > However, I still believe that we should do something -std=gnu. Hm, reject? One can't declare a procedure with one type on one side, and another different type on the other side and expect things to work. We don't support passing integer as real, or real as integer, we shouldn't support integer as logical. For what it's worth, I think there should be no logical kind. To store integer or real values, it makes sense to leave the choice to the user depending on the range of the data, but to store only two different possible values, really it's a target-dependent choice that should be left to the compiler. Anyway, I'm in favor of rejecting by default. Mikael