From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Regexp bytecode disassembler Date: Sun, 22 Mar 2020 18:55:53 +0200 Message-ID: <83imiwcorq.fsf@gnu.org> References: <4201DF24-BCC4-4C08-9857-38207B7C10B4@acm.org> <83mu8bdriv.fsf@gnu.org> <68FB4EC3-3C67-4D07-8473-5FC671024515@acm.org> <834kuhecsr.fsf@gnu.org> <875zex79bx.fsf@gmail.com> <83y2rtcux2.fsf@gnu.org> <871rpl77zy.fsf@gmail.com> <83r1xkcwbk.fsf@gnu.org> <87sgi05u2w.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="61690"; mail-complaints-to="usenet@ciao.gmane.io" Cc: mattiase@acm.org, emacs-devel@gnu.org To: =?utf-8?B?xaB0xJtww6FuIE7Em21lYw==?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Mar 22 17:56:35 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jG3tr-000FyM-Ih for ged-emacs-devel@m.gmane-mx.org; Sun, 22 Mar 2020 17:56:35 +0100 Original-Received: from localhost ([::1]:48242 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jG3tq-0007mq-Ky for ged-emacs-devel@m.gmane-mx.org; Sun, 22 Mar 2020 12:56:34 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48688) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jG3tD-0007Ip-6K for emacs-devel@gnu.org; Sun, 22 Mar 2020 12:55:56 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:36845) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jG3tD-0004nh-2z; Sun, 22 Mar 2020 12:55:55 -0400 Original-Received: from [176.228.60.248] (port=1355 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jG3tC-0005aF-6u; Sun, 22 Mar 2020 12:55:54 -0400 In-Reply-To: <87sgi05u2w.fsf@gmail.com> (message from =?utf-8?B?xaB0xJtw?= =?utf-8?B?w6FuIE7Em21lYw==?= on Sun, 22 Mar 2020 15:43:03 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:245676 Archived-At: > From: Štěpán Němec > Cc: mattiase@acm.org, emacs-devel@gnu.org > Date: Sun, 22 Mar 2020 15:43:03 +0100 > > IMHO the complexity of `pcase' is completely transparent in this case: I disagree. And please also consider the easiness (or lack thereof) of changing the code, not just reading it. pcase is far from being simple, its syntax is tricky to understand fully. it's no accident that it took us 2-3 iterations and many discussions to converge on what is now its documentation. Just the volume of that documentation should tell you how NOT transparent is its complexity. > you can easily check the expansion e.g. with M-x > pp-macroexpand-last-sexp So you are saying that reading code should be accompanied by expanding the macros it uses? (Assuming the reader even knows about pp-macroexpand-last-sexp.) Seriously, I don't think this is something I'd call "code that explains itself". In any language.