Yuki Kimoto

• Website: d.hatena.ne.jp/perlcodesample
• About: I'm Perl Programmer. I LOVE Perl. I want to contribute Perl community and Perl users.

Recent Actions

• Commented on Thinking and Question of The Proposal for Perl 7 - day1
  Don't you know that the one who rebuilt Israel is the one that remains? Is it possible to stand by the remaining Perl Users who contributing Perl much?...
• Commented on Thinking and Question of The Proposal for Perl 7 - day1
  I think denial and power do not produce any good fruit. Is it possible to stand by me and have a constructive talking? Even in difficult times, I find it useful to discover good fruits and talk with each other....
• Commented on Perl 7: A Risk-Benefit Analysis
  I also totally agree with your comments and proposals above. (except one thing new syntax try catch, no multidimentional, signature is after v7.1). use v7; means use strict; use warnings; use utf8; and enable all features until now except feature...
• Posted From the user perspective, Perl strings have no bugs and work well. to Yuki Kimoto Perl Blog

  I feel that in the upcoming version of Perl, the core team fixes the Unicode bug as a reason to break backward compatibility Perl 5.

  Unicode in Perl internally has some inconsistencies due to conflicts between latin-1 and UTF-8.

  this is true.

  On the other hand, from the use…

• Commented on Thinking and Question of The Proposal for Perl 7 - day1
  I want to talk a lot about the positive aspects of Perl 5. I welcome positive and constructive comments....
• Commented on Thinking and Question of The Proposal for Perl 7 - day1
  If you are interested in Perl good points, see my "Perl Philosophy" site. https://translate.google.co.jp/translate?hl=ja&sl=ja&tl=en&u=https%3A%2F%2Fphilosophy.perlzemi.com%2F You will find many positive points. And why not message it?...
• Commented on Thinking and Question of The Proposal for Perl 7 - day1
  At least, 2018 to 2020, In Japan, Perl's reputation has improved for the stability....
• Commented on Thinking and Question of The Proposal for Perl 7 - day1
  Who is making Perl even worse by writing negative comments? Perl 5 has over a hundred advantages, but employers have no way of knowing about it since many people keep increasing negative messages about Perl....
• Commented on Thinking and Question of The Proposal for Perl 7 - day1
  > However its users have declined and declined. This is not. Maybe you only see TIBOE and stackoverflow information. You maybe get much negative information of Perl from other people. >While companies happily rewrite their software in to languages that...
• Posted Thinking and Question of The Proposal for Perl 7 - day1 to Yuki Kimoto Perl Blog

  I write my thinking and question about Proposal for Perl 7.

  The Proposal for Perl 7

  1. MAJOR version when you make incompatible API changes,

  First of all, I am wondering about this …

• Posted I plan to release SPVM 1.0 at the end of July. to Yuki Kimoto Perl Blog

  I plan to release SPVM 1.0 at the end of July.

  SPVM

  If you have any feedback on the bugs or features, please contact Github Issue or kimoto.yuki@gmail.com

  
  

• Commented on +1 "use v7;" in Perl 7
  Perl One Liner is one main part of Perl in Linux/Unix Server Engineer! I hope one code works well in every environment....
• Commented on Handling Perl character codes is very easy even for beginners.
  The only safe advice here is to know the encoding of your input data and decode from that to Perl strings. Yes! That is completely right. and I have forgot windows each country default encoding....
• Posted Handling Perl character codes is very easy even for beginners. to Yuki Kimoto Perl Blog

  I feel that Perl users are losing confidence because of negative feedback from other communities.

  The opinions of people who intend to harm Perl are 99% useless in my experience.

  Handling character codes is actually simple.

  Because all you have to do is remember the followi…

• Posted +1 "use v7;" in Perl 7 to Yuki Kimoto Perl Blog

  As one of Perl user, +1 "use v7;" in newer version of Perl.

  The use v syntax is worth it.

  use v5.14
  

  This syntax is the history of Perl and is also a mechanism for maintaining backward compatibility with newer versions of Perl.

  The reason this was not used is…

• Posted Create PDF using Perl/PDF::API2 to Yuki Kimoto Perl Blog

  I wrote a practical and detailed description of Perl's PDF::API2.

  It turns out that PDF::API2 is a library for performing necessary and sufficient PDF operations.

  ="https://translate.google.co.jp/translate?hl=ja&sl=ja&tl=en&u=…

• Posted Larry said "No one sews a patch of unshrunk cloth on an old garment" to Yuki Kimoto Perl Blog

  When he aproved Raku naming change, Larry said .

  "No one sews a patch of unshrunk cloth on an old garment, for the patch will pull away from the garment, making the tear worse. Neither do people pour new wine into old wineskins. If they do, the skins will burst; the wine will run out and t…

• Commented on Dancer2 0.300000 released
  Combination Dancer2 with Type::Tiny!...
• Posted Default value expression in subroutine signatures to Yuki Kimoto Perl Blog

  In first proposal of subroutine signatures, default value is the following.

  sub func($foo //= 0, $bar ||= 0) {
    
  }
  

  I think this can use only "=" as same as many ohter languages. and "||" is in body if needed.

  sub func($foo = 0, $bar) {
    $bar ||= 0;
  }
  

  …

• Commented on Type Constraints using Type::Tiny and attribute handler of subroutine signatures
  I understand your suggestion now. It means using UNIVERSAL to standardize the case of objects and the case of non-objects (Str, Num) In Perl, not everything is an object, so it would be nice if users could handle object types...
• Commented on Type Constraints using Type::Tiny and attribute handler of subroutine signatures
  Current Type::Tiny parameters check seems subroutine reference. sub add_child { state $check = compile( Object, Object ); # method signature my ($self, $child) = $check->(@_); # unpack @_ push @{ $self->children }, $child; return $self; } Your proposal is different...
• Commented on Type Constraints using Type::Tiny and attribute handler of subroutine signatures
  Can I write your idea $type->check($var) or Carp::croak($type->get_message($var)); to my blog?...
• Commented on Type Constraints using Type::Tiny and attribute handler of subroutine signatures
  I have some questions. Is my understanding is right? Syntax: $var is $type means 1: $type is object $type->check($var) or Carp::croak($type->get_message($var)); 2: $type is package name(for example, Point) blessed($var) && $var->isa('Point')...
• Commented on Type Constraints using Type::Tiny and attribute handler of subroutine signatures
  is means $type->check($var) or Carp::croak($type->get_message($var)); I think it's pretty good and simple to avoiding the method call and optimization. ":" means "is" by default, do you think it? sub foo ($num is Type) is same as by default. sub foo...
• Commented on Type Constraints using Type::Tiny and attribute handler of subroutine signatures
  Toby Are you want to use Type::Tiny with subroutine signatures?...
• Commented on Type Constraints using Type::Tiny and attribute handler of subroutine signatures
  Thank you for information. I try to read the discussion....
• Posted Type Constraints using Type::Tiny and attribute handler of subroutine signatures to Yuki Kimoto Perl Blog

  If you can perform type checking with an attribute handler and Type::Tiny, Perl will be more attractive.

  For example.

  use Type::Tiny::Signatures;
  
  sub foo ($str : Str, $num : Int) {
  
    
  
  }
  
  

• Commented on Long time no see
  I hope the surgery will be successful...
• Posted The way that CPAN authors use subroutine signatures in natural to Yuki Kimoto Perl Blog

  Perl's new feature is for the new Perl, but when it comes to subroutine signatures, CPAN Author also maybe wants to use it.

  If CPAN authors can use subroutine signatures, both application code and CPAN module code can be written in one source.

  I think new features should work with …

• Posted Is the new grammar easy to google search? to Yuki Kimoto Perl Blog

  Is the new grammar of subroutine signatures easy to google search?

  One of the criticisms of Perl is that "it cannot search google because it has many symbols".

  Increasing the number of difficult-to-search symbols also increases the blame for Perl.

  ="https://yuki-kimo…

Comment Threads

• Dave Cross commented on Thinking and Question of The Proposal for Perl 7 - day1

  > At least, 2018 to 2020, In Japan,
  > Perl's reputation has improved for the
  > stability.

  But we're not talking about reputation. We're talking about the level of usage.

• Kyouto Naomoto commented on Thinking and Question of The Proposal for Perl 7 - day1

  And it's not truth. I don't know how "at least" is this,
  

  Most of job about Perl is to maintnain the code or add functions. People didn't need to talk about Perl, because of its stability. "reputation" had never even been appeared in positive or negative. Many famous Japanese Perl Mongers had seemed to begin to learn other technology. Their activity about Perl had been getting lesser and lesser. I think, it is same as London which Dave wrote.

  I believe aggressive…

• Paul "LeoNerd" Evans commented on Perl 7: A Risk-Benefit Analysis

  A huge +1 to all of this. Thank you for articulating it so coherently. I am in entire agreement with this whole idea.

• Dean commented on Perl 7: A Risk-Benefit Analysis

  Why not introduce a warning if 'use warnings' is enabled and there is no 'use vXXXX'

  Thats a soft way to encourage using a version number AND it generally wouldnt impact one liners

• cae32 commented on Perl 7: A Risk-Benefit Analysis

  Всё так. perl тем и отличается от остальных, что хранит совместимость с килограммами написанного кода. Что гласит старая мудрость? Работает - не трогай.