From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24886 invoked by alias); 24 Apr 2014 20:45:27 -0000 Mailing-List: contact gsl-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gsl-discuss-owner@sourceware.org Received: (qmail 24875 invoked by uid 89); 24 Apr 2014 20:45:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wi0-f175.google.com Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Thu, 24 Apr 2014 20:45:25 +0000 Received: by mail-wi0-f175.google.com with SMTP id cc10so1742255wib.2 for ; Thu, 24 Apr 2014 13:45:22 -0700 (PDT) X-Received: by 10.194.122.6 with SMTP id lo6mr3466673wjb.38.1398372322589; Thu, 24 Apr 2014 13:45:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.185.141 with HTTP; Thu, 24 Apr 2014 13:45:02 -0700 (PDT) From: Rhys Ulerich Date: Thu, 24 Apr 2014 20:45:00 -0000 Message-ID: Subject: Consistently naming anonymous structs To: gsl-discuss@sourceware.org Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2014-q2/txt/msg00012.txt.bz2 Anyone know how badly things break if we changed things like typedef struct { const gsl_rng_type * type; void *state; } gsl_rng; to typedef struct gsl_rng { const gsl_rng_type * type; void *state; } gsl_rng; so that some of our opaque types might be forward declared in C++ code? - Rhys