martin

• About: Blogging about Mathematics, Programming Languages, Open-Source, Privacy, Security, Board Games, Bicycles, Classical Music, and more.

Recent Actions

• Posted Some Perl Code In Memory of a Great Scientist to martin

  On August 21, 2021, famous Polish mathematician Andrzej Schinzel passed away at the age of 84. He was one of the great minds behind modern number theory. May he rest in peace. I have extended one of my CPAN modules relating to his work and dedicated the release to his memory.

• Posted Impressions from the German Perl Workshop 2019 to martin

  Another edition of the German Perl Workshop took place in Munich from 6th to 8th March 2019. I very much enjoyed taking part. Let me share some personal remarks.

  Things I learned

  • I’ll replace my OpenSSL CLI recipes by ="https://metacpan.org/pod/IO::Socket::SSL:…
• Posted Installing sets of modules to martin

  In order to quickly install a set of Perl modules for a given task, it is nice to have some kind of meta-package serving no other purpose than pulling in a set of other more specific packages. Traditional ways of doing this with CPAN can be found in the Bundle:: and Task:: namespaces. Recent…

• Commented on The Math::BigRat Trap
  Other ideas for coping with the problem: Upgrade Math::BigInt & Math::BigRat in the core. This has already been done in perl v5.25.3. Drop Math::BigRat from the core. If you have to fetch it from CPAN, you'll get a recent release....
• Posted The Math::BigRat Trap to martin

  

  With the latest stable release of perl, v5.24.0, you could easily get trapped into using a problematic combination of math modules. Here is how, a…

• Commented on The Fuse Operator - A Suggested Language Extension
  Does Perl 6 have such an operator? Perl 6 uses the symbol ^^ for infix exclusive-or, but has no fuse operator. Interestingly, a single caret is used as a prefix and an infix operator and as a part of many...
• Commented on UTF-16 and Windows CRLF, oh my
  If you happen to process files originating from a Windows environment somewhere else, that is. In a Windows command line, the first type of quoting is required, of course....
• Commented on UTF-16 and Windows CRLF, oh my
  Beware of quoting pitfalls in a *nix shell like bash. Within doublequotes, $_ would be interpolated by the shell rather than perl. perl "-M5;binmode($_,':raw:...')for ..." should perhaps better be written as perl '-M5;binmode($_,":raw:...")for ...' in such a command line interpreter....
• Posted The Fuse Operator - A Suggested Language Extension to martin

  improvements. I would like to discuss yet another "missing" operator. Its purpose is to make expressions handle some edge cases more gracefully. It could render some other extensions that have been suggested before unnecessary. …

Comment Threads

• Yary commented on UTF-16 and Windows CRLF, oh my

  Right and in fact, in Windows cmd shell (the good old DOS-heritage one) no quoting at all is needed around the -M option, since in that shell the $ sign has no special meaning!

  And yes, this tip is good outside of Windows too- it's good anytime you need to work with files neither ASCII nor UTF8. With UTF8, the -C options can get your command-line disposable working quickly. And as a bonus it also detects UTF-16 or 32, BUT the CRLFs in my files still tripped it up, requiring me to suss out these options.

• Leon Timmermans commented on UTF-16 and Windows CRLF, oh my

  The PERLIO environmental variable may also be able to help you there.

• redcoder commented on UTF-16 and Windows CRLF, oh my

  This blog post saved my day! I was getting frustrated at my code for massaging UTF-16 XML files on Windows because I noticed extra CR being added for some reason. Changed the file open to :raw:encode(utf16) and it just worked. So easy. Came across the post on reddit. Thanks again!

• Yary commented on UTF-16 and Windows CRLF, oh my

  yay! Glad it's helping.

• pjacklam commented on The Math::BigRat Trap

  I haven't seen this blog post before now. As the maintainer of these modules, it would have been nice to know about the issues you mention.

  The distributions are a maintenance nightmare. I assume the original author did the best he could, but the quasi object oriented design is fundamentally broken. The problems caused by the broken design were "fixed" by creating shortcuts which made the modules into a mess of spaghetti code.

  In addition, it has been difficult to understand how the modules are supposed to behave. In many cases, the documentation (POD) says one thing, the com…