home.social

#perltidy — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #perltidy, aggregated by home.social.

  1. Nothing beats #Perl for not disallowed data hoarding! I may be able to finish the download of the #mysql view of Ensembl release 115 with nothing but 300 lines of #perltidy nicely formatted #Perl code. I had not done any web automation stuff in decades but I rebounded quickly.

  2. Nothing beats #Perl for not disallowed data hoarding! I may be able to finish the download of the #mysql view of Ensembl release 115 with nothing but 300 lines of #perltidy nicely formatted #Perl code. I had not done any web automation stuff in decades but I rebounded quickly.

  3. Nothing beats #Perl for not disallowed data hoarding! I may be able to finish the download of the #mysql view of Ensembl release 115 with nothing but 300 lines of #perltidy nicely formatted #Perl code. I had not done any web automation stuff in decades but I rebounded quickly.

  4. Nothing beats #Perl for not disallowed data hoarding! I may be able to finish the download of the #mysql view of Ensembl release 115 with nothing but 300 lines of #perltidy nicely formatted #Perl code. I had not done any web automation stuff in decades but I rebounded quickly.

  5. Nothing beats #Perl for not disallowed data hoarding!
    I may be able to finish the download of the #mysql view of Ensembl release 115 with nothing but 300 lines of #perltidy nicely formatted #Perl code.
    I had not done any web automation stuff in decades but I rebounded quickly.

  6. Nothing beats #Perl for not disallowed data hoarding!
    I may be able to finish the download of the #mysql view of Ensembl release 115 with nothing but 300 lines of #perltidy nicely formatted #Perl code.
    I had not done any web automation stuff in decades but I rebounded quickly.

  7. Nothing beats #Perl for not disallowed data hoarding!
    I may be able to finish the download of the #mysql view of Ensembl release 115 with nothing but 300 lines of #perltidy nicely formatted #Perl code.
    I had not done any web automation stuff in decades but I rebounded quickly.

  8. Nothing beats #Perl for not disallowed data hoarding!
    I may be able to finish the download of the #mysql view of Ensembl release 115 with nothing but 300 lines of #perltidy nicely formatted #Perl code.
    I had not done any web automation stuff in decades but I rebounded quickly.

  9. Nothing beats #Perl for not disallowed data hoarding!
    I may be able to finish the download of the #mysql view of Ensembl release 115 with nothing but 300 lines of #perltidy nicely formatted #Perl code.
    I had not done any web automation stuff in decades but I rebounded quickly.

  10. @deflarerOfClouds #GitHub has hosted #PerlTidy development for a long time. Please continue to file bug reports there: GitHub.com/perltidy/perltidy/i

    You might even consider making a reasonable case to move the project’s remaining assets off #SourceForge. Impotently whinging about it here doesn’t change anything.

    / @ChristosArgyrop @ovid @perl #Perl

  11. @deflarerOfClouds #GitHub has hosted #PerlTidy development for a long time. Please continue to file bug reports there: GitHub.com/perltidy/perltidy/i

    You might even consider making a reasonable case to move the project’s remaining assets off #SourceForge. Impotently whinging about it here doesn’t change anything.

    / @ChristosArgyrop @ovid @perl #Perl

  12. @deflarerOfClouds #GitHub has hosted #PerlTidy development for a long time. Please continue to file bug reports there: GitHub.com/perltidy/perltidy/i

    You might even consider making a reasonable case to move the project’s remaining assets off #SourceForge. Impotently whinging about it here doesn’t change anything.

    / @ChristosArgyrop @ovid @perl #Perl

  13. @deflarerOfClouds #GitHub has hosted #PerlTidy development for a long time. Please continue to file bug reports there: GitHub.com/perltidy/perltidy/i

    You might even consider making a reasonable case to move the project’s remaining assets off #SourceForge. Impotently whinging about it here doesn’t change anything.

    / @ChristosArgyrop @ovid @perl #Perl

  14. @deflarerOfClouds #GitHub has hosted #PerlTidy development for a long time. Please continue to file bug reports there: GitHub.com/perltidy/perltidy/i

    You might even consider making a reasonable case to move the project’s remaining assets off #SourceForge. Impotently whinging about it here doesn’t change anything.

    / @ChristosArgyrop @ovid @perl #Perl

  15. @eliasp @ColinTheMathmo BTW #Perl has two well-known tools to encourage and enforce #programming style and best practices, respectively:
    #PerlTidy: perltidy.github.io/perltidy
    #PerlCritic: perlcritic.com

    Your project or team can use their reasonable defaults or further configure them to reflect and maintain the consistent application of your preferences. They also integrate with editors/IDEs, source control management, and author #testing.

  16. @eliasp @ColinTheMathmo BTW #Perl has two well-known tools to encourage and enforce #programming style and best practices, respectively:
    #PerlTidy: perltidy.github.io/perltidy
    #PerlCritic: perlcritic.com

    Your project or team can use their reasonable defaults or further configure them to reflect and maintain the consistent application of your preferences. They also integrate with editors/IDEs, source control management, and author #testing.

  17. @eliasp @ColinTheMathmo BTW #Perl has two well-known tools to encourage and enforce #programming style and best practices, respectively:
    #PerlTidy: perltidy.github.io/perltidy
    #PerlCritic: perlcritic.com

    Your project or team can use their reasonable defaults or further configure them to reflect and maintain the consistent application of your preferences. They also integrate with editors/IDEs, source control management, and author #testing.

  18. @eliasp @ColinTheMathmo BTW #Perl has two well-known tools to encourage and enforce #programming style and best practices, respectively:
    #PerlTidy: perltidy.github.io/perltidy
    #PerlCritic: perlcritic.com

    Your project or team can use their reasonable defaults or further configure them to reflect and maintain the consistent application of your preferences. They also integrate with editors/IDEs, source control management, and author #testing.

  19. @eliasp @ColinTheMathmo BTW #Perl has two well-known tools to encourage and enforce #programming style and best practices, respectively:
    #PerlTidy: perltidy.github.io/perltidy
    #PerlCritic: perlcritic.com

    Your project or team can use their reasonable defaults or further configure them to reflect and maintain the consistent application of your preferences. They also integrate with editors/IDEs, source control management, and author #testing.

  20. @ovid Either of the perltidy options:

    -nwrs='A'

    or

    --no-want-right-space='A'

    ought to do it. “A” is the token #perltidy uses for #Perl attribute separators according to the output of `perltidy --dump-token-types`.

    Feel free to put either in your .perltidyrc file. I prefer to use long option names as they’re more self-documenting or at least easier to search for.

  21. @ovid Either of the perltidy options:

    -nwrs='A'

    or

    --no-want-right-space='A'

    ought to do it. “A” is the token #perltidy uses for #Perl attribute separators according to the output of `perltidy --dump-token-types`.

    Feel free to put either in your .perltidyrc file. I prefer to use long option names as they’re more self-documenting or at least easier to search for.

  22. @ovid Either of the perltidy options:

    -nwrs='A'

    or

    --no-want-right-space='A'

    ought to do it. “A” is the token #perltidy uses for #Perl attribute separators according to the output of `perltidy --dump-token-types`.

    Feel free to put either in your .perltidyrc file. I prefer to use long option names as they’re more self-documenting or at least easier to search for.

  23. @ovid Either of the perltidy options:

    -nwrs='A'

    or

    --no-want-right-space='A'

    ought to do it. “A” is the token #perltidy uses for #Perl attribute separators according to the output of `perltidy --dump-token-types`.

    Feel free to put either in your .perltidyrc file. I prefer to use long option names as they’re more self-documenting or at least easier to search for.

  24. @ovid Either of the perltidy options:

    -nwrs='A'

    or

    --no-want-right-space='A'

    ought to do it. “A” is the token #perltidy uses for #Perl attribute separators according to the output of `perltidy --dump-token-types`.

    Feel free to put either in your .perltidyrc file. I prefer to use long option names as they’re more self-documenting or at least easier to search for.

  25. @jens @RL_Dane @stoerdebegga One reason I choose #Perl is its expressivity without being too “large” of a language. (This last is why I still haven’t wrapped my head around #RakuLang—they threw so much into its core.)

    I use #PerlCritic and #PerlTidy to set fairly strict defaults, but both have escape hatches for code islands that need to bend the rules for whatever reason (e.g. better modeling or critical-path performance, or sometimes fencing off legacy code to be brought up to spec later).

  26. @jens @RL_Dane @stoerdebegga One reason I choose #Perl is its expressivity without being too “large” of a language. (This last is why I still haven’t wrapped my head around #RakuLang—they threw so much into its core.)

    I use #PerlCritic and #PerlTidy to set fairly strict defaults, but both have escape hatches for code islands that need to bend the rules for whatever reason (e.g. better modeling or critical-path performance, or sometimes fencing off legacy code to be brought up to spec later).

  27. @jens @RL_Dane @stoerdebegga One reason I choose #Perl is its expressivity without being too “large” of a language. (This last is why I still haven’t wrapped my head around #RakuLang—they threw so much into its core.)

    I use #PerlCritic and #PerlTidy to set fairly strict defaults, but both have escape hatches for code islands that need to bend the rules for whatever reason (e.g. better modeling or critical-path performance, or sometimes fencing off legacy code to be brought up to spec later).

  28. @jens @RL_Dane @stoerdebegga One reason I choose #Perl is its expressivity without being too “large” of a language. (This last is why I still haven’t wrapped my head around #RakuLang—they threw so much into its core.)

    I use #PerlCritic and #PerlTidy to set fairly strict defaults, but both have escape hatches for code islands that need to bend the rules for whatever reason (e.g. better modeling or critical-path performance, or sometimes fencing off legacy code to be brought up to spec later).

  29. @jens @RL_Dane @stoerdebegga One reason I choose #Perl is its expressivity without being too “large” of a language. (This last is why I still haven’t wrapped my head around #RakuLang—they threw so much into its core.)

    I use #PerlCritic and #PerlTidy to set fairly strict defaults, but both have escape hatches for code islands that need to bend the rules for whatever reason (e.g. better modeling or critical-path performance, or sometimes fencing off legacy code to be brought up to spec later).

  30. @jens @RL_Dane @stoerdebegga (I also think every #CPAN distribution should include #perltidy and #perlcritic configs and author tests to encourage consistently-written contributions.)

  31. @jens @RL_Dane @stoerdebegga (I also think every #CPAN distribution should include #perltidy and #perlcritic configs and author tests to encourage consistently-written contributions.)

  32. @jens @RL_Dane @stoerdebegga (I also think every #CPAN distribution should include #perltidy and #perlcritic configs and author tests to encourage consistently-written contributions.)

  33. @jens @RL_Dane @stoerdebegga (I also think every #CPAN distribution should include #perltidy and #perlcritic configs and author tests to encourage consistently-written contributions.)

  34. @jens @RL_Dane @stoerdebegga (I also think every #CPAN distribution should include #perltidy and #perlcritic configs and author tests to encourage consistently-written contributions.)

  35. @chrisjrob @snonux @Perl #PerlTidy and #PerlCritic also help with readable, maintainable, and consistent #Perl code. I like to joke that I don’t have a style, I have a perlcritic policy.

  36. @chrisjrob @snonux @Perl #PerlTidy and #PerlCritic also help with readable, maintainable, and consistent #Perl code. I like to joke that I don’t have a style, I have a perlcritic policy.

  37. @chrisjrob @snonux @Perl #PerlTidy and #PerlCritic also help with readable, maintainable, and consistent #Perl code. I like to joke that I don’t have a style, I have a perlcritic policy.

  38. @chrisjrob @snonux @Perl #PerlTidy and #PerlCritic also help with readable, maintainable, and consistent #Perl code. I like to joke that I don’t have a style, I have a perlcritic policy.

  39. @chrisjrob @snonux @Perl #PerlTidy and #PerlCritic also help with readable, maintainable, and consistent #Perl code. I like to joke that I don’t have a style, I have a perlcritic policy.