220 41219 article Path: news.gmane.org!.POSTED!not-for-mail From: masse.nicolas@gmail.com Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Modules and preambule, just why? Date: Wed, 5 Dec 2018 10:46:58 -0800 (PST) Lines: 77 Approved: news@gmane.org Message-ID: References: <16989401-2f0d-4200-997e-0ac60b47bec3@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_12_1062633911.1544035619133" X-Trace: blaine.gmane.org 1544035499 24995 195.159.176.226 (5 Dec 2018 18:44:59 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 5 Dec 2018 18:44:59 +0000 (UTC) To: ISO C++ Standard - Future Proposals Original-X-From: std-proposals+bncBCCJBHV4UALBBJF2UDQAKGQENZ37PFY@isocpp.org Wed Dec 05 19:44:54 2018 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-yb1-f200.google.com ([209.85.219.200]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gUcAF-0006HX-2h for gclcip-std-proposals@m.gmane.org; Wed, 05 Dec 2018 19:44:51 +0100 Original-Received: by mail-yb1-f200.google.com with SMTP id x199-v6sf13498961ybg.20 for ; Wed, 05 Dec 2018 10:47:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=lzgwMaLJIz+2v7xuy2aYu5h2GV+PL6DJSNMNeZAtVY4=; b=gReysEZ4XEAPbhR5fbfL9g+fdELUQncQhLpO662M68CvJB2uayvVPKB5BP1VZYRURu XnVmQLIsBNj7uGFgm+05J6xOephu44ra4mKTa0f81HLIfYo4npSQ8GvF101dkRnDod+T 4CUFmR8WncC2pbIa1A4gQj3cA9P92SMa8y+ZeejXIYHoGND83rZpJQ1bCf5p44gVvBc+ 36VDJNKMRGwP4R2HLZ6BvS9XMYvotD19ypmAC36z3WH+mhhL3z0cqpAl3EXd1GyzUyck F5WaypyTuZt2pI3tLrcj49xYIT/yfvh1tk7u2LW8EYOkXxph0x6JbABIqGBwakfC74Uc UWdw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=lzgwMaLJIz+2v7xuy2aYu5h2GV+PL6DJSNMNeZAtVY4=; b=gPx6SOupwmJIWACY3bJvTdLkZadygH224SDEbXBmIbp/T+7DtJ3IlBlZsOFzZLfQl4 HLzysyErb0uMWO9WcYQJfZ7rvqtJHiOHeNcoRWWucxmFJYlUYzfs1Jvd7O9jf4ploPNi xGGNEbq/tJzxfXOVFqRVxuvwpEyG7zmetWxl6/OPjAPZXM44XVqcKKYyAjsNvry1Gb9f iIbHAloDLkwbS9YnfP34iuLxfBqXTAioy/B9IYDEtsiQWR6A33H+WBPh6AwKloIzESO2 ugw2rENOk3/gPXNeK55TYtWHnKR7ADodq0pOjZqZHUjs+hy8F7U7scGHC2Zy19xTE9n6 F+7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version:x-original-sender:reply-to:precedence :mailing-list:list-id:x-spam-checked-in-group:list-post:list-help :list-archive:list-subscribe:list-unsubscribe; bh=lzgwMaLJIz+2v7xuy2aYu5h2GV+PL6DJSNMNeZAtVY4=; b=lZDESpxInz/gsupITd5GK9uuZVOwB46f9Z8sv4ixx3x0EBIl4PFzKzJZGKteYRONQd GDLF4R2WpsPFTzjsyuSSesQgTFpKONJm+yMk+FgizZYFgnoMzxzQsL5zkfhHqpBlK/Li qn/dUFoSzca5ZmUp5raoa5FZGnYfn6t5a2Kh8zkz+Xupih4PPLUm4CGhlb/euNYqHSAF ZByLwhXzhf3PAo5yVCV5a6FLHL3Hng4mI+pEriU3bFxyNzKVGC330d8CN3R14zEgkIOc ixp/VHN2n2DKngYCIO1bf3DmzRE5TsOKBaXVauQtEYnkLjb+bJggoTD5WYNRlmrtqx7G kV8w== X-Gm-Message-State: AA+aEWbMVY0fBUDN0YcooFGAG73LtLBL4BkNU+zETZaAZI3rNuKC6u9q oNKlW+KKTAcBBD/dNSig4NNW7w== X-Google-Smtp-Source: AFSGD/UlpcLWnwNO5G17C/G7v1JVA25A2131oyNY1LJV4iCQiTso4GtXCskAJP459RNnvZdrgZG5CA== X-Received: by 2002:a25:4105:: with SMTP id o5mr5683687yba.34.1544035621360; Wed, 05 Dec 2018 10:47:01 -0800 (PST) X-BeenThere: std-proposals@isocpp.org Original-Received: by 2002:a81:a082:: with SMTP id x124ls13176250ywg.1.gmail; Wed, 05 Dec 2018 10:46:59 -0800 (PST) X-Received: by 2002:a81:550b:: with SMTP id j11mr357957ywb.4.1544035619744; Wed, 05 Dec 2018 10:46:59 -0800 (PST) In-Reply-To: X-Original-Sender: Masse.Nicolas@gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Spam-Checked-In-Group: std-proposals@isocpp.org X-Google-Group-Id: 399137483710 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:41219 Archived-At: ------=_Part_12_1062633911.1544035619133 Content-Type: multipart/alternative; boundary="----=_Part_13_470747068.1544035619133" ------=_Part_13_470747068.1544035619133 Content-Type: text/plain; charset="UTF-8" After reading your answer and thinking about it in the last days, I thing I understand things a bit better now. First I understand that module are far less related to the linking problem than I first tough. Also, I think I better understand how they will actually work in real world application. Still, one question remains for me: If for example you wanna ship a library. As of today, you generally with the library the headers so that people using the library will be able to compile their code and make use of the library you made. But how does it work if you wanna use modules? do you ship a module file together with the lib? And if so, how do you intend to generate this module file? Also note that even if I better understand the proposal now, my doubts about it and the need of declaring the module explicitly remains. In fact, I would have prefer an approach where the exported symbols are deduced from the code instead of having to declare it explicitly. Masse Nicolas. -- You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group. To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/a8310d69-20cb-48ba-8a8e-c62c09d4cd94%40isocpp.org. ------=_Part_13_470747068.1544035619133 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
After reading your answer and thinking about it in th= e last days, I thing I understand things a bit better now.
First = I understand that module are far less related to the linking problem than I= first tough.
Also, I think I better understand how they will act= ually work in real world application.

Still, one q= uestion remains for me:
If for example you wanna ship a library.<= /div>
As of today, you generally with the library the headers so that p= eople using the library will be able to compile their code and make use of = the library you made.
But how does it work if you wanna use modul= es? do you ship a module file together with the lib? And if so, how do you = intend to generate this module file?

Also note= that even if I better understand the proposal now, my doubts about it and = the need of declaring the module explicitly remains.
In fact, I w= ould have prefer an approach where the exported symbols are deduced from th= e code instead of having to declare it explicitly.
Masse Nicolas.

--
You received this message because you are subscribed to the Google Groups &= quot;ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposa= ls+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.= com/a/isocpp.org/d/msgid/std-proposals/a8310d69-20cb-48ba-8a8e-c62c09d4cd94= %40isocpp.org.
------=_Part_13_470747068.1544035619133-- ------=_Part_12_1062633911.1544035619133-- .