unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Reuben Thomas via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 47488@debbugs.gnu.org
Subject: bug#47488: Treatment of # in js.el
Date: Mon, 29 Mar 2021 21:28:29 +0000	[thread overview]
Message-ID: <CAOnWdoi_B9TRp3w-prbKtoLwAjQKj2rk4VGJYS4v2Rfco5sfzA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]

I started using private class fields, as described here
<https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_class_fields>
(a stage 3 proposal that is widely implemented, though not actually
standardized yet AFAICT).

These are normal fields that start with a hash.

I find in js--proper-indentation the line (annotated by git blame):

17b5d0f7077 (Chong Yidong         2009-08-14 2864)           ((eq
(char-after) ?#) 0)

It sets the indentation for a line starting with # unconditionally to 0. I
cannot find any other use of # in JavaScript that would justify treating
lines starting with # apparently like C preprocessor macros. There is other
related code, and it all seems to go back to when js.el was first installed
in Emacs.

Is this just because the code was originally based on cc-mode or something,
and the references to hash were never removed? Or was cpp used with early
JavaScript?? I see references such as js--opt-cpp-start which says "Regexp
matching the prefix of a cpp directive", and a match for "#define" in
js--update-quick-match-re.

I cannot see any code in js-tests.el that tests this cpp-related
functionality.

Is there some reason to keep the cpp-related code in js.el? I presume
removing it would simplify then adding support for private class fields;
indeed, maybe no particular support is needed if cpp support is first
removed.

-- 
https://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 3065 bytes --]

             reply	other threads:[~2021-03-29 21:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 21:28 Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-30  0:50 ` bug#47488: Treatment of # in js.el Dmitry Gutov
2021-05-08 12:43 ` Lars Ingebrigtsen
2021-05-09 11:18   ` Dmitry Gutov
2021-05-09 11:31     ` Dmitry Gutov
2021-05-10  8:29     ` Lars Ingebrigtsen
2021-05-10 12:12       ` Dmitry Gutov
2021-05-10  8:34     ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-10 12:14       ` Dmitry Gutov
2021-05-11 12:21         ` Lars Ingebrigtsen
2021-05-11 12:45           ` Dmitry Gutov
2021-05-12 13:32             ` Lars Ingebrigtsen
2021-05-12 13:53               ` Eli Zaretskii
2021-05-12 13:56                 ` Lars Ingebrigtsen
2021-05-12 14:39                 ` Andreas Schwab
2021-05-12 14:49                   ` Eli Zaretskii
2021-05-12 14:56               ` Dmitry Gutov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOnWdoi_B9TRp3w-prbKtoLwAjQKj2rk4VGJYS4v2Rfco5sfzA@mail.gmail.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=47488@debbugs.gnu.org \
    --cc=rrt@sc3d.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).