Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relax the naming rule of extension name #1662

Merged
merged 14 commits into from
Oct 3, 2024
Merged

Relax the naming rule of extension name #1662

merged 14 commits into from
Oct 3, 2024

Conversation

kersten1
Copy link
Collaborator

@kersten1 kersten1 commented Oct 2, 2024

Update from this PR - #718

Not convinced that I did the supervisor section correctly. But I'm also not convinced that it is explained in Volume II. However, volume II has grown significantly and I just do not know it all.

Signed-off-by: Kersten Richter <[email protected]>
Signed-off-by: Kersten Richter <[email protected]>
src/naming.adoc Outdated
"Zifencei2p0" name version 2.0 of same.
Standard unprivileged extensions can also be named by using a single "Z" followed by an
alphanumeric name. The name must end with an alphabetical character or an
optional version number. The second letter from the bottom cannot be a numeric if the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"a numeric" => "numeric"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"bottom" => "end"

src/naming.adoc Outdated
Other standard extensions that extend the supervisor-level architecture are
named by using ``S'' as a prefix, followed by an alphanumeric name. The name
must end with an alphabetical character or an optional
version number. The second letter from the bottom cannot be a numeric character
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"a numeric character" => "numeric"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"bottom" => "end"

src/naming.adoc Outdated
and "Xhwacha2p0" name version 2.0 of same.
Non-standard extensions are named by using a single "X" followed by the alphanumeric
name. The name must end with an alphabetic character or an optional version number. The
second letter from the bottom cannot be a numeric if the last letter is
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"a numeric" => "numeric"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"bottom" => "end"

Copy link
Member

@aswaterman aswaterman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feel free to merge after addressing my comments.

src/naming.adoc Outdated Show resolved Hide resolved
src/naming.adoc Outdated Show resolved Hide resolved
src/naming.adoc Outdated Show resolved Hide resolved
Signed-off-by: Kersten Richter <[email protected]>
Signed-off-by: Kersten Richter <[email protected]>
Signed-off-by: Kersten Richter <[email protected]>
src/naming.adoc Outdated
@@ -78,7 +78,7 @@ of the P extension.

Standard unprivileged extensions can also be named by using a single "Z" followed by an
alphanumeric name. The name must end with an alphabetical character or an
Copy link
Collaborator

@topperc topperc Oct 3, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this paragraph is combining two things together. The sentence "The name must end with an alphabetical character or an optional version number" is making version number part of the "name". But, as the "Version Numbers" section says, the version number is encoded after the name. The "name" of extensions must end in alphabetical character independent of whether there is a version number.

I think the "Version Numbering" and "Underscores" sections should be moved further down after the extension naming schemes are described. And all references to versions from the naming sections should be removed or integrated into the "Version Numbering" section.

I'm happy to work on the change.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kersten1 I'll be unavailable for a few days, but I'm happy to roll with whatever changes you and Craig agree upon. Don't wait for me to merge.

src/naming.adoc Outdated
Standard unprivileged extensions can also be named by using a single "Z" followed by an
alphanumeric name. The name must end with an alphabetical character or an
optional version number. The second letter from the end cannot be numeric if the
last letter is ``p''. For example, "Zifencei" names the instruction-fetch fence extension
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not well versed in asciidoc. Does p'' mean something? Documentation I found shows pwould be monospace, but I couldn't find anything for mixing and ''.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what is up with that either! Glad you found and fixed it.

Andrew tells me that's a LaTeX-ism.
…ng sections

Mention underscore as a separor of multi-letter extensions more
consistently.

Move the special case requiring an underscore for "P" extension to
the Version Numbering section.
src/naming.adoc Outdated Show resolved Hide resolved
src/naming.adoc Outdated Show resolved Hide resolved
@kersten1
Copy link
Collaborator Author

kersten1 commented Oct 3, 2024

@topperc Thanks! Waiting for the checks to complete and I'll merge.

@kersten1 kersten1 merged commit 1569c8d into main Oct 3, 2024
2 checks passed
@kersten1 kersten1 deleted the kersten1-patch-1 branch October 3, 2024 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants