From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Philipp Stephani Newsgroups: gmane.emacs.devel Subject: Re: Dynamic loading progress Date: Sun, 13 Sep 2015 13:04:20 +0000 Message-ID: References: <83y4oiiw81.fsf@gnu.org> <838ugdf251.fsf@gnu.org> <87bnl1vmqf.fsf@lifelogs.com> <87vbj8tow4.fsf@lifelogs.com> <87r3twtagf.fsf@lifelogs.com> <85siebl7ws.fsf@stephe-leake.org> <85a90ilwmm.fsf@stephe-leake.org> <83386a6f7z.fsf@gnu.org> <85h9upjz7v.fsf@stephe-leake.org> <83wq3k3kl4.fsf@gnu.org> <85bnkwil1c.fsf@stephe-leake.org> <83pp9cwky8.fsf@gnu.org> <85a90ggf2d.fsf@stephe-leake.org> <54E0A40F.5080603@dancol.org> <83sie7un20.fsf@gnu.org> <54E0D181.2080802@dancol.org> <83r3trulse.fsf@gnu.org> <54E0D7E0.305@[87.69.4.28]> <83h9unukbg.fsf@gnu.org> <54E0DEF8.7020901@dancol> <83egpruiyp.fsf@gnu.org> <54E0FF93.2000104@dancol.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b86df78e31731051fa09670 X-Trace: ger.gmane.org 1442149483 11963 80.91.229.3 (13 Sep 2015 13:04:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 13 Sep 2015 13:04:43 +0000 (UTC) Cc: stephen_leake@stephe-leake.org, emacs-devel@gnu.org To: Daniel Colascione , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Sep 13 15:04:37 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Zb6xQ-0003RZ-PI for ged-emacs-devel@m.gmane.org; Sun, 13 Sep 2015 15:04:36 +0200 Original-Received: from localhost ([::1]:35840 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zb6xQ-0002c2-7G for ged-emacs-devel@m.gmane.org; Sun, 13 Sep 2015 09:04:36 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42162) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zb6xN-0002bx-4u for emacs-devel@gnu.org; Sun, 13 Sep 2015 09:04:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zb6xM-0002Wo-Ds for emacs-devel@gnu.org; Sun, 13 Sep 2015 09:04:33 -0400 Original-Received: from mail-wi0-x22a.google.com ([2a00:1450:400c:c05::22a]:36106) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zb6xK-0002W4-Te; Sun, 13 Sep 2015 09:04:31 -0400 Original-Received: by wicgb1 with SMTP id gb1so110208671wic.1; Sun, 13 Sep 2015 06:04:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=cSvx64Ud2sO43bSGXmLizzPuJ13SJw3BGc8EoBDkT48=; b=OxXFrk4YNVyGI/GSRPWiuNGFPaBwNU45CNoQICBXa/8FcrjG5E3KCJsdXQJdN04yNn n8gFsiQ3MPC1mRX9FnkVisAvCNiCqr6A4t8rifyTSvFSdbMnKEWL3zPbv1N0el7VBRyr H7fQBSLj0y88YqnU/xzZEpBrpLwhkPDSAtESFxCYCmhd7KbQ042nib/5dgJ3icNW26mk FNYmrIVI0T+g6TqoGWA86OZkOcqrtfiGFGXiYMf20+hSkXwEI0x3oUdS3nW9SZ1zMvFs TEf21WVihLqtvOeGWP7ESzfxjpIvS7IAmrBXR/bR5cM8EG/ljcoXdPeg1ou+a/G+GHKg lqpQ== X-Received: by 10.194.201.130 with SMTP id ka2mr18567960wjc.79.1442149470245; Sun, 13 Sep 2015 06:04:30 -0700 (PDT) In-Reply-To: <54E0FF93.2000104@dancol.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c05::22a X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:189886 Archived-At: --047d7b86df78e31731051fa09670 Content-Type: text/plain; charset=UTF-8 Daniel Colascione schrieb am So., 15. Feb. 2015 um 21:21 Uhr: > typedef struct emacs_value_tag* emacs_value; > Would it make sense to not use a typedef here? Using a typedef means that the type including its size is opaque and subject to change, which can break ABI compatibility. I'd rather have something like: struct emacs_value { // contains private fields }; and then pass *struct emacs_value** around. --047d7b86df78e31731051fa09670 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Daniel Colasci= one <dancol@dancol.org> schr= ieb am So., 15. Feb. 2015 um 21:21=C2=A0Uhr:
=C2=A0 typedef struct emacs_value_tag* emacs_value;

Would it make sense to not use a typedef h= ere? Using a typedef means that the type including its size is opaque and s= ubject to change, which can break ABI compatibility. I'd rather have so= mething like:

struct emacs_value {
=C2= =A0 // contains private fields
};

and th= en pass=C2=A0struct emacs_value*=C2=A0around.
--047d7b86df78e31731051fa09670--