From: Soham Gumaste <sohamg2@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New Package: p4_16-mode
Date: Sat, 18 Nov 2023 15:20:55 -0600 [thread overview]
Message-ID: <CAAr-Hh1k5St4BfQLNZm3w6ZxKBKhrTc-2ojVOzb92kVJk_7i+g@mail.gmail.com> (raw)
In-Reply-To: <87sf52zryw.fsf@posteo.net>
> As mentioned in the last thread, I don't know if "p4_16" is a technical
> term, but I know that it is an unusual symbol name, so I want to make
> sure if it would be possible to call it p4-16 or something like that
> instead.
>
Apologies for forgetting to reply to that part. So the language itself
goes by "p4" or "p4lang" (think go/golang). The _14 and _16 refer to
different diverging versions of the language. P4_14 is officially
abandoned/deprecated (think python 2.7) and P4_16 is the "current
revision of the p4 language" [1].
That being said, I think "p4-16-mode" is clear enough to indicate
which version is being implied and we could/should take the liberty to
change the _ to a -. I am of the opinion that the "16" bit is
necessary as the language itself is evolving. I do not see an issue
with "p4-16-mode".
Thanks
[1]: https://p4.org/specs/
--
Soham Gumaste
sohamg2@gmail.com
next prev parent reply other threads:[~2023-11-18 21:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 20:31 [ELPA] New Package: p4_16-mode Soham Gumaste
2023-11-17 7:36 ` Philip Kaludercic
2023-11-17 20:11 ` Soham Gumaste
2023-11-18 21:12 ` Philip Kaludercic
2023-11-18 21:20 ` Soham Gumaste [this message]
2023-11-18 21:28 ` Soham Gumaste
2023-11-18 21:51 ` Philip Kaludercic
2023-11-18 22:18 ` Soham Gumaste
2023-11-20 18:09 ` Soham Gumaste
2023-11-23 5:57 ` Philip Kaludercic
-- strict thread matches above, loose matches on Subject: below --
2023-11-15 6:29 Pedro Andres Aranda Gutierrez
2023-11-15 17:23 ` Soham Gumaste
2023-11-23 20:06 ` sohamg2
2023-11-24 6:17 ` Pedro Andres Aranda Gutierrez
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAr-Hh1k5St4BfQLNZm3w6ZxKBKhrTc-2ojVOzb92kVJk_7i+g@mail.gmail.com \
--to=sohamg2@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.