Path to raku by lizmat · Pull Request #89 · Raku/problem-solving (original) (raw)

El sáb., 17 ago. 2019 a las 13:19, Aleks-Daniel Jakimenko-Aleksejev (< notifications@github.com>) escribió:

***@***.**** commented on this pull request. ------------------------------ In solutions/language/PATH-TO-RAKU.md <#89 (comment)>: > +As some packagers have already done, the executable should be called `raku`. +With symlinks / hard links added as appropriate to keep the old executable +names working. If at all technically possible, running a script using the +`perl6` as the executor, should provide a DEPRECATED warning at some point. + +Since `rakudo` is the name of the implementation, the main executable that +is created in the build process should have that name. `raku` and `perl6` +should be symlinks. + +### Extensions + +The extension `.rk` for scripts, `.rkm` for modules, and `.rd` for +documentation (POD6) will become the defacto standards for files containing +`Raku` code or documentation. The old `.pm`, `.pm6` and `.pod6` extensions +will continue to be supported for 6.e. In 6.f, the `.pm`, `.pm6` and `.pod6` +extensions should be marked as DEPRECATED, causing a message to be generated As I mentioned previously, I hate “POD6” with passion. It's two things that don't mean anything clumped together (a useless abbreviation + a number from the language name that we won't longer use). I was extremely happy to see .rd because it allows us to actually call it RakuDoc now (something that will be obvious to most of the readers), and moreover .rd seems to be unused by anything else and it somewhat even resembles .md. I'm OK with not changing it now, but I'll be pushing to change it later anyway, so might as well fix it right away.

OK, I'm all for working code and rough consensus. One of my arguments for keeping Pod6 is that Pod6 classes are named Pod, so if you propose a new name for the Slang, you need to propose a new name for these classes too. So what do you think about RND? It's Raku New Documentation (as opposed to Plain (or Perl) old documentation), we can use .rnd as the extension, and RND for the class names. Which would actually be nice, since now we're using different acronyms for them. .RND files are rare also. On the other hand, we can also use .rd for documentation and RakuDoc for the class hierarchy. So I'll resolve this issue. No big deal.