ysth

• Website: ysth.info
• About: Round

Recent Actions

• Commented on Ready, Set, Compile... you slow Camel
  Note that in 2014 ingy and davido provided Inline::Module, which moves Inline compilation to module install time....
• Commented on GitHub and the Perl License
  The CopyFilesFromBuild plugin can be used to include build files in the repo. But for something static like licenses probably easier to not create them during build....
• Commented on List Assignment in Scalar Context
  Very nice article (other than misspelling my name :) ). ( my ($required1, $required2, $optional) = @ARGV ) >= 2 or die ... (but always use Getopt::Long for argument parsing)...

Comment Threads

• Tom Wyant commented on GitHub and the Perl License

  Update: under CPAN Licensing Guidelines, The Perl and Raku Foundation recommends that dual-licensed packages put each license in a separate file in a LICENSES/ directory. Does this recommendation need to change?

• Mikko Koivunalho commented on GitHub and the Perl License

  For certain other policy files, such as CONTRIBUTING and CODE_OF_CONDUCT, GitHub allows three different locations:

  - The .github folder
  - The root of the repository
  - The docs folder

  But this DOES NOT APPLY to LICENSE-* files!

  https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file

  As for GitLab and other repository hosting providers…

• raf commented on GitHub and the Perl License

  It seems a bit flaky. It didn't work for me with LICENSE-Artistic-1.0 and LICENSE-GPL-1 ("the same terms as the Perl 5 programming language system itself"). Github only recognized the Artistic. Replacing LICENSE-GPL-1 with LICENSE-GPL-2 made github only recognize GPL-2. It only recognizes both when there is Artistic-2.0 and GPL-3.

  And github ignores the LICENSES directory.

  I use the REUSE Specification for licenses:

  REUSE - Make licensing easy for everyone
  https://reuse.software/

  I don't know if it's well-sup…

• Leon Timmermans commented on Ready, Set, Compile... you slow Camel

  > Note that in 2014 ingy and davido provided Inline::Module, which moves Inline compilation to module install time.

  Yeah that. I would avoid any tool that requires a compiler in production environments; that's just a no-go.

  Also, it sounds to me like the use of custom OPs is wrong; you can't use them for anything that binds late (like methods or subrefs), you have to know for sure in advance exactly what is being called (like function calls).

• Toby Inkster commented on Ready, Set, Compile... you slow Camel

  Also, it sounds to me like the use of custom OPs is wrong; you can't use them for anything that binds late (like methods or subrefs), you have to know for sure in advance exactly what is being called (like function calls).

  They are being used for function calls. However, I'd say if you're accessing objects using function calls, you're not really doing object-oriented programming any more as you've lost polymorphism which is a defining feature of the paradigm.