[ELPA] New Package: p4_16-mode

[ELPA] New Package: p4_16-mode

[Soham Gumaste]

Hello Emacs Devs,

I am writing to ask that my package "p4_16-mode.el" be added to ELPA.
The repo is at the following link:

https://github.com/SohamG/p4_16-mode.el

Summary:
P4 (Programming Protocol Independent Packet Processors) is a domain
specific language used to program network fabric devices like NICs or
switches. The project can be found at https://p4.org . This package
adds a major mode for this language. This mode was initially a part of
the github repo "p4lang/tutorials" (Apache 2.0). I have added some
polish, and obtained permission from the repo maintainers to submit
here.

I do not have write access to the ELPA git repo. Please let me know if
I need to make any modifications.

Thanks
-- 
Soham Gumaste
sohamg2@gmail.com

Re: [ELPA] New Package: p4_16-mode

[Philip Kaludercic]

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

Soham Gumaste <sohamg2@gmail.com> writes:

> Hello Emacs Devs,
>
> I am writing to ask that my package "p4_16-mode.el" be added to ELPA.
> The repo is at the following link:
>
> https://github.com/SohamG/p4_16-mode.el

Here are a few quick changes I'd propose:


[-- Attachment #2: Type: text/plain, Size: 8632 bytes --]

diff --git a/p4_16-mode.el b/p4_16-mode.el
index 23c2825..f9d146b 100644
--- a/p4_16-mode.el
+++ b/p4_16-mode.el
@@ -3,26 +3,42 @@
 ;; Author: Soham S Gumaste <sohamg2@gmail.com>
 ;; Maintainer: Soham S Gumaste <sohamg2@gmail.com>
 ;; Created: 11 Nov 2023
-;; Original Source: https://github.com/p4lang/tutorials/blob/master/vm/p4_16-mode.el
-;; Original License: Apache 2.0
-;; Original Author: Vladimir Gurevich <vladimir.gurevich@barefootnetworks.com>
-;; Modifications bylicensed under the same license OR the MIT License.
+;; Modifications bilicensed under the same license OR the MIT License.
 
 ;; Keywords: languages p4_16
 
 ;; This file is not part of GNU Emacs.
 
-;; This file is free software…
-;; …
-;; along with this file.  If not, see <https://www.gnu.org/licenses/>.
+;; This program is free software; you can redistribute it and/or modify
+;; it under the terms of the GNU General Public License as published by
+;; the Free Software Foundation, either version 3 of the License, or
+;; (at your option) any later version.
+
+;; This program is distributed in the hope that it will be useful,
+;; but WITHOUT ANY WARRANTY; without even the implied warranty of
+;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+;; GNU General Public License for more details.
+
+;; You should have received a copy of the GNU General Public License
+;; along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
 ;;; Commentary:
+
 ;; P4 (Programming Protocol Independent Packet Processors) is a domain
 ;; specific language designed to program network fabric devices.
 ;; This mode has preliminary support for P4_16. It covers the core language,
 ;; but it is not clear yet, how we can highlight the indentifiers, defined
-;; for a particular architecture. Core library definitions are included
+;; for a particular architecture.  Core library definitions are included
 
+;;; History:
+
+;; The headers above have no special meaning, and could also be
+;; re-written in prose under a special section.  Also, was the package
+;; really created just a few days ago?
+
+;; Original Source: https://github.com/p4lang/tutorials/blob/master/vm/p4_16-mode.el
+;; Original License: Apache 2.0
+;; Original Author: Vladimir Gurevich <vladimir.gurevich@barefootnetworks.com>
 
 ;;; Code:
 (defvar p4_16-mode-hook nil)
@@ -30,46 +46,46 @@
 ;; Define the keymap (for now it is pretty much default)
 (defvar p4_16-mode-map
   (let ((map (make-keymap)))
-    (define-key map "\C-j" 'newline-and-indent)
+    (define-key map (kbd "C-j") 'newline-and-indent)
     map)
-  "Keymap for P4_16 major mode")
+  "Keymap for P4_16 major mode.")
 
-;; Syntactic HighLighting
+;;; Syntactic Highlighting
 
-;; Main keywords (declarations and operators)
+;;;; Main keywords (declarations and operators)
 (defconst p4_16-keywords
-      '("action" "apply"
-        "control"
-        "default"
-        "else" "enum" "extern" "exit"
-        "header" "header_union"
-        "if"
-        "match_kind"
-        "package" "parser"
-        "return"
-        "select" "state" "struct" "switch"
-        "table"  "transition" "tuple" "typedef"
-        "verify")
-      "P4_16 Standard Keywords")
+  '("action" "apply"
+    "control"
+    "default"
+    "else" "enum" "extern" "exit"
+    "header" "header_union"
+    "if"
+    "match_kind"
+    "package" "parser"
+    "return"
+    "select" "state" "struct" "switch"
+    "table"  "transition" "tuple" "typedef"
+    "verify")
+  "P4_16 Standard Keywords.")
 
 (defconst p4_16-annotations
   '("@name" "@metadata" "@alias")
-  "P4_16 Standard Annotations")
+  "P4_16 Standard Annotations.")
 
 (defconst p4_16-attributes
-      '("const" "in" "inout" "out"
-        ;; Tables
-        "key" "actions" "default_action" "entries" "implementation"
-        "counters" "meters")
-      "P4_16 Object Attributes and Access Specifiers")
+  '("const" "in" "inout" "out"
+    ;; Tables
+    "key" "actions" "default_action" "entries" "implementation"
+    "counters" "meters")
+  "P4_16 Object Attributes and Access Specifiers.")
 
 (defconst p4_16-variables
   '("packet_in" "packet_out")
-  "P4_16 Packet Types")
+  "P4_16 Packet Types.")
 
 (defconst p4_16-operations
   '("&&&" ".." "++" "?" ":")
-  "P4_16 Operators")
+  "P4_16 Operators.")
 
 (defconst p4_16-constants
   '(;; Don't care
@@ -83,11 +99,11 @@
     "exact" "ternary" "lpm" "range"
     ;; We can add constants for supported architectures here
     )
-  "P4_16 Standard Constants")
+  "P4_16 Standard Constants.")
 
 (defconst p4_16-types
   '("bit" "bool" "int" "varbit" "void" "error")
-  "P4_16 Standard Datatypes")
+  "P4_16 Standard Datatypes.")
 
 (defconst p4_16-primitives
   '(;; Header methods
@@ -102,37 +118,36 @@
     "accept" "reject"
     ;; misc
     "NoAction")
-  "P4_16 Standard Primitives")
+  "P4_16 Standard Primitives.")
 
 (defconst p4_16-cpp
-      '("#include"
-        "#define" "#undef"
-        "#if" "#ifdef" "#ifndef"
-        "#elif" "#else"
-        "#endif"
-        "defined"
-        "#line" "#file"))
+  '("#include"
+    "#define" "#undef"
+    "#if" "#ifdef" "#ifndef"
+    "#elif" "#else"
+    "#endif"
+    "defined"
+    "#line" "#file"))
 
 (defconst p4_16-cppwarn
-      '("#error" "#warning"))
+  '("#error" "#warning"))
 
 ;; Optimize the strings
-(setq p4_16-keywords-regexp    (regexp-opt p4_16-keywords   'words))
-(setq p4_16-annotations-regexp (regexp-opt p4_16-annotations     1))
-(setq p4_16-attributes-regexp  (regexp-opt p4_16-attributes 'words))
-(setq p4_16-variables-regexp   (regexp-opt p4_16-variables  'words))
-(setq p4_16-operations-regexp  (regexp-opt p4_16-operations 'words))
-(setq p4_16-constants-regexp   (regexp-opt p4_16-constants  'words))
-(setq p4_16-types-regexp       (regexp-opt p4_16-types      'words))
-(setq p4_16-primitives-regexp  (regexp-opt p4_16-primitives 'words))
-(setq p4_16-cpp-regexp         (regexp-opt p4_16-cpp        1))
-(setq p4_16-cppwarn-regexp     (regexp-opt p4_16-cppwarn    1))
-
+(defvar p4_16-keywords-regexp    (regexp-opt p4_16-keywords   'words))
+(defvar p4_16-annotations-regexp (regexp-opt p4_16-annotations     1))
+(defvar p4_16-attributes-regexp  (regexp-opt p4_16-attributes 'words))
+(defvar p4_16-variables-regexp   (regexp-opt p4_16-variables  'words))
+(defvar p4_16-operations-regexp  (regexp-opt p4_16-operations 'words))
+(defvar p4_16-constants-regexp   (regexp-opt p4_16-constants  'words))
+(defvar p4_16-types-regexp       (regexp-opt p4_16-types      'words))
+(defvar p4_16-primitives-regexp  (regexp-opt p4_16-primitives 'words))
+(defvar p4_16-cpp-regexp         (regexp-opt p4_16-cpp        1))
+(defvar p4_16-cppwarn-regexp     (regexp-opt p4_16-cppwarn    1))
 
 ;; create the list for font-lock.
 ;; each category of keyword is given a particular face
 (defconst p4_16-font-lock-keywords
-  (list
+  (list					;Perhaps use backquoting?
    (cons p4_16-cpp-regexp         font-lock-preprocessor-face)
    (cons p4_16-cppwarn-regexp     font-lock-warning-face)
    (cons p4_16-types-regexp       font-lock-type-face)
@@ -154,16 +169,16 @@
    (cons "\\([^_A-Za-z][+-]?\\([0-9]+w\\)?[0-9]+\\)"    font-lock-constant-face)
    ;;(cons "\\(\\w*\\)"        font-lock-variable-name-face)
    )
-  "Default Highlighting Expressions for P4_16")
+  "Default Highlighting Expressions for P4_16.")
 
 (defvar p4_16-mode-syntax-table
   (let ((st (make-syntax-table)))
     (modify-syntax-entry  ?_  "w"      st)
     (modify-syntax-entry  ?/  ". 124b" st)
     (modify-syntax-entry  ?*  ". 23"   st)
-    (modify-syntax-entry  ?\n  "> b"   st)
+    (modify-syntax-entry  ?\n "> b"    st)
     st)
-  "Syntax table for p4_16-mode")
+  "Syntax table for p4_16-mode.")
 
 ;;; Indentation
 (defvar p4_16-indent-offset 4
@@ -192,7 +207,7 @@
 
 ;; Put everything together
 (defun p4_16-mode ()
-  "Major mode for editing P4_16 programs"
+  "Major mode for editing P4_16 programs."
   (interactive)
   (kill-all-local-variables)
   (set-syntax-table p4_16-mode-syntax-table)
@@ -201,8 +216,8 @@
   (set (make-local-variable 'indent-line-function) 'p4_16-indent-line)
   (setq major-mode 'p4_16-mode)
   (setq mode-name "P4_16")
-  (with-eval-after-load "xcscope" (cscope-minor-mode))
+  (when (fboundp 'cscope-minor-mode) (cscope-minor-mode))
   (run-hooks 'p4_16-mode-hook))
 
-;; The most important line
 (provide 'p4_16-mode)
+;;; p4_16-mode.el ends here

[-- Attachment #3: Type: text/plain, Size: 742 bytes --]


Also, would it be imaginable to rename it to p4-16-mode?  The mid-symbol
underscore looks unusual in a Lisp context

> Summary:
> P4 (Programming Protocol Independent Packet Processors) is a domain
> specific language used to program network fabric devices like NICs or
> switches. The project can be found at https://p4.org . This package
> adds a major mode for this language. This mode was initially a part of
> the github repo "p4lang/tutorials" (Apache 2.0). I have added some
> polish, and obtained permission from the repo maintainers to submit
> here.

I suppose you want to add the package to NonGNU ELPA then?

> I do not have write access to the ELPA git repo. Please let me know if
> I need to make any modifications.
>
> Thanks

Re: [ELPA] New Package: p4_16-mode

[Soham Gumaste]

> +;;; History:
> +
> +;; The headers above have no special meaning, and could also be
> +;; re-written in prose under a special section.  Also, was the package
> +;; really created just a few days ago?
> +

I mean, moved the file into a repo of its own on that day, and began making some
modifications to better suit ELPA. The original file has a date from 2017.
Should I use that instead?

>
> I suppose you want to add the package to NonGNU ELPA then?
>

I was not familiar with the distinction between GNU ELPA and NonGNU
ELPA. But now
that I have read up a bit, NonGNU ELPA does fit better.

I have applied your patch, thanks for taking the time to help me with it.
Please let me know if any further changes are needed, or if I need to
create a new thread to submit to NonGNU ELPA.

Thanks

-- 
Soham Gumaste
sohamg2@gmail.com

Re: [ELPA] New Package: p4_16-mode

[Philip Kaludercic]

Soham Gumaste <sohamg2@gmail.com> writes:

>> +;;; History:
>> +
>> +;; The headers above have no special meaning, and could also be
>> +;; re-written in prose under a special section.  Also, was the package
>> +;; really created just a few days ago?
>> +
>
> I mean, moved the file into a repo of its own on that day, and began making some
> modifications to better suit ELPA. The original file has a date from 2017.
> Should I use that instead?

I think that would reflect the history better.

>>
>> I suppose you want to add the package to NonGNU ELPA then?
>>
>
> I was not familiar with the distinction between GNU ELPA and NonGNU
> ELPA. But now
> that I have read up a bit, NonGNU ELPA does fit better.

OK.

> I have applied your patch, thanks for taking the time to help me with it.
> Please let me know if any further changes are needed, or if I need to
> create a new thread to submit to NonGNU ELPA.

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.

> Thanks

-- 
Philip Kaludercic

Re: [ELPA] New Package: p4_16-mode

[Soham Gumaste]

> 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

Re: [ELPA] New Package: p4_16-mode

[Soham Gumaste]

I have updated the git repo accordingly.

Re: [ELPA] New Package: p4_16-mode

[Philip Kaludercic]

Soham Gumaste <sohamg2@gmail.com> writes:

>> 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".

OK, the only thing which I believe is missing now is a "Version" tag in
the package header (see (info "(elisp) Simple Packages")).  A new
version of every ELPA package is released whenever a commit touches that
line.

> Thanks
>
> [1]: https://p4.org/specs/

-- 
Philip Kaludercic

Re: [ELPA] New Package: p4_16-mode

[Soham Gumaste]

On Sat, Nov 18, 2023 at 3:51 PM Philip Kaludercic <philipk@posteo.net> wrote:
> OK, the only thing which I believe is missing now is a "Version" tag in
> the package header (see (info "(elisp) Simple Packages")).  A new
> version of every ELPA package is released whenever a commit touches that
> line.
>

I have added a Version header. Setting it to "0.3" since the original
file had a Version header with value "0.2". Hope that works.


-- 
Soham Gumaste
sohamg2@gmail.com

Re: [ELPA] New Package: p4_16-mode

[Soham Gumaste]

Hello Philip,

I was wondering if I get some notification that the package has been
added to NonGNU ELPA. I am new to the "mailing list world" and was
wondering what the process looks like. I guess I will eventually see a
commit adding the package on savannah. Anyway, I don't mean to rush.

Thanks

Re: [ELPA] New Package: p4_16-mode

[Philip Kaludercic]

Soham Gumaste <sohamg2@gmail.com> writes:

> Hello Philip,
>
> I was wondering if I get some notification that the package has been
> added to NonGNU ELPA. 

You (or whatever address is listed under maintainer) will receive a
message every time a new release is made.  I have just been
unfortunately busy the last few weeks so I got delayed, sorry about
that.

>                       I am new to the "mailing list world" and was
> wondering what the process looks like. I guess I will eventually see a
> commit adding the package on savannah. Anyway, I don't mean to rush.

Basically yes, I just had to add the package specification to
elpa-packages.  There is no magic here in the "mailing list world" :^)

> Thanks

[ELPA] New Package: p4_16-mode

[Pedro Andres Aranda Gutierrez]

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

Hi,

I've been using this functionality and would strongly support adding it.
It would be yet another argument for Emacs for some of our students ;-)

Thanks, Soham

My .2 cents, /PA

-- 
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet

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

Re: [ELPA] New Package: p4_16-mode

[Soham Gumaste]

On Wed, Nov 15, 2023 at 12:29 AM Pedro Andres Aranda Gutierrez
<paaguti@gmail.com> wrote:
>
> Hi,
>
> I've been using this functionality and would strongly support adding it.
> It would be yet another argument for Emacs for some of our students ;-)
>
> Thanks, Soham
>
> My .2 cents, /PA
>

Hello Pedro,

Thanks for the support. I must credit Vladimir Gurevich for laying the
foundation.

In addition, I am trying to write a relatively simple
completion-at-point-function for p4_16 (mostly to procrastinate on
homework). Depending on how that goes, Emacs will be even more
lucrative for P4 development!

Thanks

-- 
Soham Gumaste
sohamg2@gmail.com

Re: [ELPA] New Package: p4_16-mode

[sohamg2]

Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:

> Hi,
>
> I've been using this functionality and would strongly support adding it.
> It would be yet another argument for Emacs for some of our students ;-)
>
> Thanks, Soham
>
> My .2 cents, /PA

Hello Pedro,

Writing to inform that the mode has been added to NonGNU elpa. Hopefully
your students find Emacs more attractive now!

Re: [ELPA] New Package: p4_16-mode

[Pedro Andres Aranda Gutierrez]

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

Hey Soham

Good news, I'll keep you posted.

Best, /PA

On Thu, 23 Nov 2023 at 21:07, <sohamg2@gmail.com> wrote:

>
> Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
>
> > Hi,
> >
> > I've been using this functionality and would strongly support adding it.
> > It would be yet another argument for Emacs for some of our students ;-)
> >
> > Thanks, Soham
> >
> > My .2 cents, /PA
>
> Hello Pedro,
>
> Writing to inform that the mode has been added to NonGNU elpa. Hopefully
> your students find Emacs more attractive now!
>


-- 
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet

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