Added perl keywords - #8
Conversation
|
Hey, so I've waffled on this one for a couple of days for the same reason I haven't yet added Perl to this already -- what they call a keyword does not necessarily mesh with the definition of a keyword being used in the other tracked languages, and I haven't quite determined an appropriate line yet. For example: included on this list is a list of functions, but the other language lists don't (to my knowledge anyway -- I'll admit I'm not sure about Visual Basic include global or builtin functions. Same thing with variables. So yeah, I'm not ignoring you, just considering whether the list appropriately meets the definition as is, because aside from being potentially "incorrect", even if I merged this as is with the intent of iterating on it it would make the visualization useless due to the sheer number. On the technical side of things, you are correct, only the yaml is required, the README and graph are built with CI in the push. |
|
That makes sense. I was a little worried after I found the whole list of
keywords and saw its way more than any other language besides visual basic
maybe.
If I may ask what is the current definition of a keyword you are using for
the other languages?
The perl keywords page has several section of keywords and if it makes
sense maybe we can throw out some of these keywords so it better fits your
definition
…On Sun, Oct 9, 2022 at 12:03 PM Nick Meyer ***@***.***> wrote:
Hey, so I've waffled on this one for a couple of days for the same reason
I haven't yet added Perl to this -- what they call a keyword does not
necessarily mesh with the definition of a keyword being used in the other
tracked languages, and I haven't quite determined an appropriate line yet.
For example: included on this list is a list of functions, but the other
language lists don't (to my knowledge anyway -- I'll admit I'm not sure
about Visual Basic include global or builtin functions. Same thing with
variables.
So yeah, I'm not ignoring you, just considering whether the list
appropriately meets the definition as is, because aside from being
potentially "incorrect", even if I merged this as is with the intent of
iterating on it it would make the visualization useless due to the sheer
number.
—
Reply to this email directly, view it on GitHub
<#8 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHDIA32J2A77YJ6CORMSFH3WCMCHLANCNFSM6AAAAAAQ7BYUHU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
2 participants
I have added the the perl keywords to the chart.yaml file but was unsure if I needed to update the README as well or if that auto generated.
Looking at past commits only the yaml file was updated.