From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15908 invoked by alias); 2 Feb 2007 19:20:45 -0000 Received: (qmail 15442 invoked by alias); 2 Feb 2007 19:20:25 -0000 Date: Fri, 02 Feb 2007 19:20:00 -0000 Message-ID: <20070202192025.15441.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/30625] Array pointers to components of derived type arrays do not work In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "paulthomas2 at wanadoo dot fr" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-02/txt/msg00171.txt.bz2 ------- Comment #5 from paulthomas2 at wanadoo dot fr 2007-02-02 19:20 ------- Subject: Re: Array pointers to components of derived type arrays do not work dfranke at gcc dot gnu dot org wrote: > ------- Comment #4 from dfranke at gcc dot gnu dot org 2007-02-01 11:28 ------- > As I came across this once more: is it possible to issue a compile-time warning > that "array pointers to components of derived type arrays" are allowed by the > standard but are not yet implemented in gfortran (gfc_todo, maybe)? > > This would prevent some users (e.g. me) from using it right now. If otherwise > the code compiles fine, one silently gets unusable results ... > > > Daniel, I'll see what I can come up with - I have also been feeling round the edges of how this might be cured. Implementation of F2003 classes will require another field in the descriptor. I am trying to figure out how best to do this without completely breaking the library API but I am attempting to design this field to fulfill both functions. Best regards Paul -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30625