-
Notifications
You must be signed in to change notification settings - Fork 8
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
[BUG] Perl6 code examples should be removed from Perl #218
Comments
Hi Valentin!
Sure, I'd be happy to fix the Perl 6 code and identify things that should be removed.
This site was a cool idea. I've had fun filling in the gaps. As a retired software engineer I take on projects like this to keep my brain working. It's surprising how tricky some of these are, especially with a language like Perl -- whose philosophy is "there's more than one way to do anything".
Do you have any recommendations for a free platform to put code demos? (I noticed some of them don't work.)
One thing that would be nice is a way to filter the Language Coverage list so that only the empty entries are shown. Or to sort the column.
How are the columns sorted, by the way? Not by id or idiom title, that's for sure!
Regards,
Gary
- Gary
…________________________________
From: Valentin Deleplace ***@***.***>
Sent: Sunday, October 30, 2022 6:28:36 PM
To: Deleplace/programming-idioms ***@***.***>
Cc: Gary Puckering ***@***.***>; Author ***@***.***>
Subject: Re: [Deleplace/programming-idioms] [BUG] Perl6 code examples should be removed from Perl (Issue #218)
Hi Gary, thank you so much for all your recent contributions.
Yes I agree, any snippet specific to Perl6/Raku is not appropriate as a "Perl" entry, and should be fixed (jump back to Perl5 compat) or deleted.
If you know how to modify them directly to match Perl5, please do so.
If you can help me with a list of implementation IDs to be deleted, I will be happy as an Admin to delete them.
Sometimes an Idiom has multiple implementations for the same language, which is why it's important to find the specific implementation ID to be deleted (e.g. by clicking on the impl language name near the idiom title)
[image]<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F13508141%2F198904586-842ff171-cb85-42af-a081-53e331ff0ecf.png&data=05%7C01%7C%7C6fad1302a564420a8b1d08dabac616e7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638027657193735981%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FJpgAlfz0FaLrfM5XBG1zZ%2Fs3zEPhz%2B4BVeTjBo%2B6Ds%3D&reserved=0>
—
Reply to this email directly, view it on GitHub<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.luolix.top%2FDeleplace%2Fprogramming-idioms%2Fissues%2F218%23issuecomment-1296365525&data=05%7C01%7C%7C6fad1302a564420a8b1d08dabac616e7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638027657193735981%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rSsE03ZhRnNSPpsYGj%2FCPNxNbsKOing05AeaWM981qw%3D&reserved=0>, or unsubscribe<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.luolix.top%2Fnotifications%2Funsubscribe-auth%2FABKV26DOOPAWH7VAVQAC4P3WF3SAJANCNFSM6AAAAAARSM5JGI&data=05%7C01%7C%7C6fad1302a564420a8b1d08dabac616e7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638027657193735981%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=na2RU3qxVrO9v9Qk%2FsLtNIbevh4QTP9wDk0lbtnHIZU%3D&reserved=0>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
When there's more than one way to do it, and they are all acceptable, then we can have several of them, no problem. The visitor will read them, maybe test them, and figure out which one best fits their needs. codepad.org is really cool and simple, however
The alternative wandbox.org is really cool too! I recommend it. To discover missing entries, as a contributor: have a look at the Perl Backlog. It shows a random sample of things to complete, different when you refresh. The Language Coverage page shows first the columns of your "favorite languages", in green. In the subsequent columns, the languages are sorted by completeness: 1 point for an snippet, 1 point for a doc link, 1 point for a demo link. I agree with the sentiment "some simple things are tricky to implement" - and also it takes times! Often more than 15mn for a correct implementation, with documentation, and with a runnable demo. |
Question: what does clicking the Flag button do? And is that documented anywhere? |
It's "flagging" in the sense of "reporting a problem".
If you see something very unambiguously fixable (e.g. a typo), the best is
to fix it by editing the implementation entry.
If you think the snippet is okay but there's a better way to achieve the
goal, the best is to create a new distinct entry (not to overwrite the
existing suboptimal one).
If you see something plain wrong and can't fix it, you click the Flag
button, explain why, and I (the admin) will see what we can do with it.
Often the correct action is will be to delete the entry, and only an admin
can do that.
Le lun. 31 oct. 2022 à 16:56, Gary Puckering ***@***.***> a
écrit :
… Question: what does clicking the Flag button do? And is that documented
anywhere?
—
Reply to this email directly, view it on GitHub
<#218 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADHB4LPQLI4H7YV2JI3PNNLWF7T2XANCNFSM6AAAAAARSM5JGI>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
I’ve been going through the Perl code idioms, filling in many that were missing, when I noticed that there are some that are specific to Perl 6 — which is now named Raku and which is a different language than Perl 5. See idiom #50 for an example.
Perl 5 and Perl6/Raku have officially diverged are now going their separate ways. Having Perl 6 code intermixed with Perl 5 examples is confusing.
Perhaps there should be a language entry for Raku and the Perl 6 code examples relocated.
At a minimum the Perl 6 code examples under Perl should be removed.
The text was updated successfully, but these errors were encountered: