220 41210 <7a8fde63-330f-42e6-b4e6-47695158c463@isocpp.org> article Path: news.gmane.org!.POSTED!not-for-mail From: inkwizytoryankes@gmail.com Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Why module is module? Date: Mon, 3 Dec 2018 12:41:08 -0800 (PST) Lines: 209 Approved: news@gmane.org Message-ID: <7a8fde63-330f-42e6-b4e6-47695158c463@isocpp.org> References: Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_4276_243321021.1543869669032" X-Trace: blaine.gmane.org 1543869547 24574 195.159.176.226 (3 Dec 2018 20:39:07 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 3 Dec 2018 20:39:07 +0000 (UTC) To: ISO C++ Standard - Future Proposals Original-X-From: std-proposals+bncBDDLTAGNTIBBBZVJS3QAKGQEOIMHBVY@isocpp.org Mon Dec 03 21:39:03 2018 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-yw1-f70.google.com ([209.85.161.70]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gTuzc-0006E2-Sf for gclcip-std-proposals@m.gmane.org; Mon, 03 Dec 2018 21:39:01 +0100 Original-Received: by mail-yw1-f70.google.com with SMTP id l131sf10106236ywc.21 for ; Mon, 03 Dec 2018 12:41:11 -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=IC5yy5SKDafLr8RfaYr348e7fAL4dDFQGgUI+jYvuNU=; b=LJtvY5cEgkvR3qN+SgWy++AyIO6LnZLx5EWZ9nsPWhzalOcEtxAMh6lJPRQGx1bHoJ NVSa0owAz6GvY7T6sKhAscbxl96KvzsuVAcPhvigdUwKotubARHkVsYiMGdoPcLvkXYX wfAmXaYi/zIQrgZ/235Cas6EnZEWFtW0LmTHODqNNRoYtbT4Y/O4pWYznrdELFjDHZFS NjPKaQmldfEEOccS2N5OuasJcP/KMMgFlfO8+VQA2sqwueRodODcDvYF6nqZiLp/hNju ub+SwuIr/YOmRbs8EuCyMHLNn9XK+v3k2BTOUDPeKbqJhWMaDoIx8NojOhNq0lbraJ72 0h9A== 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=IC5yy5SKDafLr8RfaYr348e7fAL4dDFQGgUI+jYvuNU=; b=iI1/BJM7ijR8t0zrXOzxl5H0zoWrfsOXaf8+VQ0Ea6xzwl7ggiIJtjo0GTp+XzxpWG zfWzyHcVlwlMwaFQYsoeyg3zKZuKGZdLmyjonXN6YKj0eUxWhY7mwx8pkA/gYMKMs2ii J5Ev/KHcBfwMXHGAN2UdiXq0gWFK+CyO2OoBRqnuFgQHfznmxVxzBRYwxfVE4q52nxBP 3d2Sl2NyQ2ueun6JagLZg91vh7ErqwfndI8ENiPl/ABPcdb5C7bkGnAdGtYWLZIrpyGe 6FT0wYxK6Y5yAwTOaOZaBh3U2wgjkEgfb8WbSb8JTVVYZFZKt6y03LG1HDKoWMJQFRGh yfZg== 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=IC5yy5SKDafLr8RfaYr348e7fAL4dDFQGgUI+jYvuNU=; b=CSnQXiol8JGyzINrLGk6Xn+1ANKUYjpwsW70IPN8C3t5LU8JTCJCV4N1rTaYOt8KMj VzJ9uVd7TAPSh6Rg2L7w/FaVQDjqak7CsRJWiAKjooMT+AvqNtvEHM0F5ox+05bcrzwY Jvre+wTMANsrV9S956AUuUwIM8/7fuxDLxPxiqxNbuTkGz8+poEJlPNjLE3YH6e1iATi Ql84zDR+kgfb0L/yLy8OaNPLUKwDDhIOJm1GBunVzjXsmQw82RvKGTRPRPDbjq0AktJy jqEfKDn7nHv/h9mCBCE+3WhVnLv/o6lOdaidy75CAHoZ7slfS3CgBolIfL/YxhzVKfQp rRTg== X-Gm-Message-State: AA+aEWZ2DtgF6HBD2ASmkL5T+ySCp2q/CY4eht2Nto4QytDZEhOjtplB 4FXEV0o+wIOWQ+mFZ+65VmlkMA== X-Google-Smtp-Source: AFSGD/VaKfbII+Pd7SQZ01UoRYlHIYHpVrx80+W5z7aC/M7EfTIfP3HD7qdrhyFfbBaNrCjYEaIsmg== X-Received: by 2002:a25:ac90:: with SMTP id x16-v6mr10758156ybi.3.1543869671274; Mon, 03 Dec 2018 12:41:11 -0800 (PST) X-BeenThere: std-proposals@isocpp.org Original-Received: by 2002:a5b:605:: with SMTP id d5-v6ls2756708ybq.5.gmail; Mon, 03 Dec 2018 12:41:09 -0800 (PST) X-Received: by 2002:a25:d14a:: with SMTP id i71mr59480ybg.2.1543869669663; Mon, 03 Dec 2018 12:41:09 -0800 (PST) In-Reply-To: X-Original-Sender: inkwizytoryankes@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:41210 Archived-At: ------=_Part_4276_243321021.1543869669032 Content-Type: multipart/alternative; boundary="----=_Part_4277_1085795742.1543869669032" ------=_Part_4277_1085795742.1543869669032 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Saturday, December 1, 2018 at 6:40:40 PM UTC+1, Klaim - Jo=C3=ABl Lamott= e=20 wrote: > > Here is the paper that was approved: http://wg21.link/p0924=20 > On Sat, 1 Dec 2018 at 15:13, Klaim - Jo=C3=ABl Lamotte > wrote:=20 > >=20 > > My understanding is that the issue have been solved by one of the=20 > > papers processed at last meeting,=20 > > making the module a context-specific keyword, in the module preamble=20 > > to be exact.=20 > > That's from memory, I' can't search for the exact paper and=20 > > confirmation right now.=20 > I'm aware of paper (even I mention exactly same number in my message), my= =20 question was different. Why in first place this exactly name was taken and when problems arise name= =20 was not change to something else? As less serious solution could use `_Module` :) Overall I bit dislike another corner case in language. In long run better= =20 would be if module was intruded by some unique keyword and not by special= =20 case (if you define variable with type `module` you get module unit). =20 > > On Fri, 30 Nov 2018 at 20:45, >=20 > wrote:=20 > > >=20 > > > Some people do not like fact that `module` will be keyword (because i= t=20 > will clash with existing names).=20 > > >=20 > > > One solution is p0924r0 where it will make context sensitive.=20 > > >=20 > > > But we could choose different name too (that are less likely to=20 > clash). Eg.=20 > > > begin_module X;=20 > > > start_module Y; //or=20 > > > export_module Z; //or=20 > > > module_unit W; //or=20 > > >=20 > > > It will be bit more to type but this will be done only couple of time= s=20 > per file (and in many cases done by IDE).=20 > > >=20 > > > Why this approach was not taken?=20 > > >=20 > > > Another way could be add `using`:=20 > > >=20 > > > using module X;=20 > > > export using module Y; //and=20 > > >=20 > > > But this could be read as `import` similar to how we using `using=20 > namespace Z;`=20 > > >=20 > > > --=20 > > > You received this message because you are subscribed to the Google=20 > Groups "ISO C++ Standard - Future Proposals" group.=20 > > > To unsubscribe from this group and stop receiving emails from it, sen= d=20 > an email to std-proposal...@isocpp.org .=20 > > > To post to this group, send email to std-pr...@isocpp.org=20 > .=20 > > > To view this discussion on the web visit=20 > https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/d9cdd3db-837= 2-47b1-a8b4-f98bf6136b63%40isocpp.org.=20 > > --=20 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 e= mail 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/7a8fde63-330f-42e6-b4e6-47695158c463%40isocpp.or= g. ------=_Part_4277_1085795742.1543869669032 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Saturday, December 1, 2018 at 6:40:40 PM UTC+1,= Klaim - Jo=C3=ABl Lamotte wrote:
Here is the paper that was approved: http://wg21.link/p0924
On Sat, 1 Dec 2018 at 15:13, Klaim - Jo=C3=ABl Lamotte <mjk...@gmail.com<= /a>> wrote:
>
> My understanding is that the issue have been solved by one of the
> papers processed at last meeting,
> making the module a context-specific keyword, in the module preamb= le
> to be exact.
> That's from memory, I' can't search for the exact pape= r and
> confirmation right now.



> On Fri, 30 No= v 2018 at 20:45, <inkwizyt...@gmail.com> wrote:
> >
> > Some people do not like fact that `module` will be keyword (b= ecause it will clash with existing names).
> >
> > One solution is p0924r0 where it will make context sensitive.
> >
> > But we could choose different name too (that are less likely = to clash). Eg.
> > begin_module X;
> > start_module Y; //or
> > export_module Z; //or
> > module_unit W; //or
> >
> > It will be bit more to type but this will be done only couple= of times per file (and in many cases done by IDE).
> >
> > Why this approach was not taken?
> >
> > Another way could be add `using`:
> >
> > using module X;
> > export using module Y; //and
> >
> > But this could be read as `import` similar to how we using `u= sing namespace Z;`
> >
> > --
> > You received this message because you are subscribed to the G= oogle Groups "ISO C++ Standard - Future Proposals" group.
> > To unsubscribe from this group and stop receiving emails from= it, send an email to std-proposal...@isocpp.org.
> > To post to this group, send email to std-pr...@isocpp.org.
> > To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-propo= sals/d9cdd3db-8372-47b1-a8b4-f98bf6136b63%40isocpp.org.

--
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/7a8fde63-330f-42e6-b4e6-47695158c463= %40isocpp.org.
------=_Part_4277_1085795742.1543869669032-- ------=_Part_4276_243321021.1543869669032-- .