From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: :alnum: broken? Date: Sun, 23 Feb 2020 08:52:52 -0800 (PST) Message-ID: <855ba386-373c-4946-b903-00f9eb6a0a97@default> References: <<86wo8flqct.fsf@stephe-leake.org>> <> <<86sgj3ljf0.fsf@stephe-leake.org>> <> <<18bd2b64-1c2f-055f-4fa0-092bdb1da531@cs.ucla.edu>> <<838sktibpu.fsf@gnu.org>> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="58352"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stephen_leake@stephe-leake.org, rms@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii , Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Feb 23 17:53:53 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 1j5uVt-000F6t-5U for ged-emacs-devel@m.gmane-mx.org; Sun, 23 Feb 2020 17:53:53 +0100 Original-Received: from localhost ([::1]:54648 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j5uVs-0001vi-62 for ged-emacs-devel@m.gmane-mx.org; Sun, 23 Feb 2020 11:53:52 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33682) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j5uVI-0001Nm-Jx for emacs-devel@gnu.org; Sun, 23 Feb 2020 11:53:17 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j5uVH-0002yd-BR for emacs-devel@gnu.org; Sun, 23 Feb 2020 11:53:16 -0500 Original-Received: from aserp2120.oracle.com ([141.146.126.78]:34296) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1j5uVF-0002xV-VR; Sun, 23 Feb 2020 11:53:14 -0500 Original-Received: from pps.filterd (aserp2120.oracle.com [127.0.0.1]) by aserp2120.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 01NGlpP6195812; Sun, 23 Feb 2020 16:53:01 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : cc : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2020-01-29; bh=EtR+nvV7jOaN1irLCkNsOXBrX0vCUqzdleIovHLSDnc=; b=SGX4r/XrMAkLY/QBi5y1mJJNjHb89DT97W8t0Rv5doYMo9jZelvc2uV80YM2ia8ptdE7 SfCoGUhzhACvhkW4rSLAaiwoCqtL7hNKQY/P3ZKKM0ukjXRJR2z9NrU0g3vIRKBg6LB3 NJ63l9kAjsU38OEwhvEjcpa3sX5HqIR2zcBCEvQmdMpfyurqDuTDfPAo/wrWZ7QmL6ru y/jUCLMH6L1qCwUN8L2lgmEvNHwsovyB+6cDFezQH6/+MFANTDgft47T1TikLVcIyJiU 455ynJgMG+Sh0t/qgZ/9Xly61Mr1s+HR0HtfYe8XweQ0BoKc5G92Zv4n4V6c/e23QUjk Wg== Original-Received: from aserp3020.oracle.com (aserp3020.oracle.com [141.146.126.70]) by aserp2120.oracle.com with ESMTP id 2ybvr4g1v1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sun, 23 Feb 2020 16:53:01 +0000 Original-Received: from pps.filterd (aserp3020.oracle.com [127.0.0.1]) by aserp3020.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 01NGr1dO036604; Sun, 23 Feb 2020 16:53:01 GMT Original-Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserp3020.oracle.com with ESMTP id 2ybe3cdvu9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sun, 23 Feb 2020 16:53:01 +0000 Original-Received: from abhmp0013.oracle.com (abhmp0013.oracle.com [141.146.116.19]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id 01NGqr3L004831; Sun, 23 Feb 2020 16:52:53 GMT In-Reply-To: <<838sktibpu.fsf@gnu.org>> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.4966.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9540 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 bulkscore=0 mlxlogscore=999 spamscore=0 malwarescore=0 mlxscore=0 phishscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2001150001 definitions=main-2002230140 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9540 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=999 spamscore=0 clxscore=1011 adultscore=0 lowpriorityscore=0 malwarescore=0 priorityscore=1501 mlxscore=0 impostorscore=0 suspectscore=0 phishscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2001150001 definitions=main-2002230139 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] [fuzzy] X-Received-From: 141.146.126.78 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:245044 Archived-At: > > signal an error for patterns like [:alnum:]. >=20 > AFAIU, Richard suggested to emit a warning from the byte compiler. > That might be a good-enough solution, better than signaling an error > at run time, IMO. +1. Not only better, but appropriate. It should be a warning, because it is not an invalid regexp. It might generally be a useless regexp, and it's most likely not what the user intended, but it's not invalid. Raising an error would, well, be an error, IMHO. Displaying a warning during byte-compilation would be very helpful.