Download as PDF, PPTX
![Rate [num/sec]
100
75
50
25
0
97
18
Perl::Critic Perl::Lint](https://image.slidesharecdn.com/perl-lintyetanotherperlsourcecodelinter-140829012712-phpapp01/75/Perl-Lint-Yet-Another-Perl-Source-Code-Linter-68-2048.jpg)
![Rate [num/sec]
100
75
About 50
400% increase
25
0
97
18
Perl::Critic Perl::Lint](https://image.slidesharecdn.com/perl-lintyetanotherperlsourcecodelinter-140829012712-phpapp01/75/Perl-Lint-Yet-Another-Perl-Source-Code-Linter-69-2048.jpg)
More Related Content
Similar to Perl::Lint - Yet Another Perl Source Code Linter
![Vibe Coding vs. Spec-Driven Development [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/vibecodingvsspecdrivendevelopment-251209105622-43f455e7-thumbnail.jpg?width=640&height=640&fit=bounds)
Perl::Lint - Yet Another Perl Source Code Linter
- 1. Perl::Lint - YetAnother Perl Source Code Linter http://bit.ly/1p5HdSA @moznion
- 2.
- 3. SEE ALSO Perlの静的解析入門と Perlリファクタリングツール App::PRTのご紹介 @hitode909 ! Day 2, 多目的教室3, 16:00
- 4.
- 5.
- 6. Perl::Lint ! https://github.com/moznion/Perl-Lint https://metacpan.org/release/MOZNION/Perl- Lint-0.01_01 (<= UNDERDEVELOPMENT!!!)
- 7. Perl::Lint ! https://github.com/moznion/Perl-Lint https://metacpan.org/release/MOZNION/Perl- Lint-0.01_02 (<= UNDERDEVELOPMENT!!!)
- 8.
- 9. A. Source CodeLinter for Perl
- 10. Yes, It’s like… Perl:: http://bit.ly/1l5HrYX
- 11. Are you using Perl::Critic? http://bit.ly/1pfMxCW
- 12.
- 13. A. Source CodeLinter for Perl
- 14.
- 15. What is SourceCode Linter???
- 16. A. Analyzes the source code and detects the causes of bugs
- 17. Search and Destroy http://bit.ly/1AT3Bl3
- 18.
- 19. There are fivebad things
- 20. There are fivebad things
- 21. There are fivebad things
- 22. There are fivebad things
- 23. There are fivebad things
- 24. There are fivebad things
- 25.
- 26. Is this whatI think it is?
- 27. It’s just CODEREVIEW?
- 28. But do youthink human should do the such code review?
- 29. Human should work more creative
- 30. It seems possibleto check by computer
- 31. There are fivebad things
- 32. And probably humanoverlooks
- 33.
- 34. Hard to UnderstandCode Destroy!
- 35. Hard to UnderstandCode Easy to review
- 36. Do you likeclean code, and why?
- 37. Readable code ! ! Reviewable code
- 38. Readable code ≒ ! ! Reviewable code
- 39.
- 40. Maintainable code willbe growing up along maintainable
- 41. Humans can focuson creative work
- 42. Okay, Make maintainablecode by computer!
- 43. And then sourcecode linter was appeared (1979 for C)
- 44. Now; js-lint, find-bugs, rubocop, etc…
- 45. And language processors: Go, Scala and etc.
- 46.
- 48.
- 49. Perl::Critic checks thecode conform to PBP style or not
- 50. Benefit to analyze code by computer
- 51.
- 52.
- 53. He don’t takea mistake
- 54. He is fast (in many cases)
- 55.
- 56. Cost of human:HIGH ! Cost of computer: LOW
- 57. Cost of human:HIGH ! Cost of computer: LOW Good!!
- 58.
- 59. But… If thereis Perl::Critic, Is Perl::Lint don’t need?
- 60. Perl::Critic is awesome but a little slow
- 61. In large project, It takes 3 minutes to run only Perl::Critic
- 62. How do youspend in meantime?
- 63. Coffee? How doyou spend in meantime?
- 64. Coffee? Chat? Howdo you spend in meantime?
- 65. Coffee? Nap? Chat? How do you spend in meantime?
- 66. Coffee? Swing Copters? Nap? Chat? How do you spend in meantime?
- 67. Life is tooshort, so let’s accelerate!!
- 68. Rate [num/sec] 100 75 50 25 0 97 18 Perl::Critic Perl::Lint
- 69. Rate [num/sec] 100 75 About 50 400% increase 25 0 97 18 Perl::Critic Perl::Lint
- 70. Yeah!!!! I'll showyou all my tricks
- 71.
- 72. Background that ledto the development
- 73. This project receive TPF grant
- 74. Do you know TPF grant?
- 75. Nozaki-san and Maki-san(@lestrrat-san) are people in a high position of TPF grant
- 76. Maki-san「日本人がトップになっ たのに日本から1つもProposal出な いのちょっとアレじゃない？」▼ me「そうですなあ」▼ Maki-san「moznion出してよ」▼ me「！！！！！」▼
- 77. Time flies everything goes…
- 79.
- 80.
- 81. Return to oursubject…
- 82. How do wedo static analyzing for Perl?
- 84.
- 85.
- 86. Two major methods - Evaluate Token - Evaluate AST
- 87. Two major methods - Evaluate Token - Evaluate AST
- 88. Tools - PPI- Compiler::Lexer
- 89. Tools - PPI- Compiler::Lexer
- 90.
- 91. *Very Fast* tokenizer made of C++
- 92. Compiler::Lexer is fast ⇛ Perl::Lint is fast!
- 93. And others: Compiler::Parser, C::CodeGenerator::LLVM, etc… @goccy54++
- 94. Example of tokens that is generated by Compiler::Lexer
- 95.
- 96.
- 97.
- 98. Use these tokens to analyze
- 100.
- 101.
- 102. Top Level +args +site_policies +lint +lint_string Policies +evaluate 1 Filters +filter 1 1 .. * 1 .. *
- 103.
- 104.
- 105. Each policies are isolated
- 106. Easy to make your own policy
- 107.
- 108. *** CAUTION *** A lot of bad code are here. Close your eyes.
- 109.
- 110.
- 111.
- 113.
- 114. Feature of Implementation and Bad Know-hows
- 115.
- 116. Use C-Style for() But PBP prohibit it!!
- 117. Use List::Util::any insteadof grep
- 118. Don’t use regex, compare by eq in series
- 119.
- 120. Function calling isalmost gone.
- 121. Use simple parts e.g. raw-bless, POPO
- 122.
- 123. Perl::Critic’s default rulesystem is a bit difficult…
- 124. Yes, I know, perlcriticrc can adjust them. But too much hustle
- 125. Perl::Lint checks theall of policies as default
- 126. And you canfilter any policies as you like
- 127.
- 128.
- 129. Yes, of course you can deny the all of policies :)
- 130. You can define your own filter
- 131.
- 132. And Perl::Lint provides default policies
- 135.
- 136. These are features of Perl::Lint
- 137. But installation issuch a hassle!
- 138.
- 139.
- 140. Meaning to publish Playground
- 141. It makes easyto get feedback
- 142.
- 143. Publish the Playground is looking good!
- 144.
- 145. Implement the allof policies…
- 146.
- 147. Module for testing (Like a Test::Perl::Critic)
- 148. Cooperate with GitHub (Like a Coveralls)
- 149. Inject the result into code as TODO comment (inspired by rubocop)
- 150. As you see, Perl::Lint is under development
- 151.
- 152. I’m looking for contributors!
- 153.
- 154.