Re^3: Check if key exist in hash but not exact match

I tinkered some more:

There was a bug which I've fixed. I've no idea why, but I'd coded for only one NO_CASE. Obviously, you can have ABC, Abc, abc, AbC, and so on.

I decided that I was doing too much work with @matches. I changed that to %matches and, instead of removing elements from the array by recreating it using grep, I'm simply using delete to remove key/value pairs. This resulted in much cleaner code and, I imagine, would be a lot more efficient.

There was also an interesting point regarding the contents of the "Value" column produced by printf. Having introduced undef values in my test data for basic edge-case checks, this meant that there was either a price (number) or '<undefined>' (string). A %s worked fine for both when the price was 1.25; however, a price of 3.00 was converted to just 3.

My introduction of undef may have been completely artificial and would never occur in the OP's data: in this case, a %.2f would probably suffice throughout. I've left the undef values as it was an interesting exercise dealing with this. I can see potential improvements here but won't go into that further unless it is something the OP really wants.

As before, I'll put the new code and another sample run in a spoiler.

— Ken

Comment on Re^3: Check if key exist in hash but not exact match Select or Download Code

Replies are listed 'Best First'.
Re^4: Check if key exist in hash but not exact match by ibm1620 (Hermit) on Apr 04, 2023 at 21:36 UTC
`my $fmt = "%-7s %-@{[max map length, keys %$hash]}s ";` [download] Definitely adding this to my snippet file! But I've never seen this syntax before. What is triggering the code evaluation of max(...) here?	[reply] [d/l]
Re^5: Check if key exist in hash but not exact match ( meaning of " @{[...]} " ) by LanX (Saint) on Apr 04, 2023 at 21:51 UTC
> What is triggering the code evaluation of max(...) here? `" @{[...]} "` is an idiomatic pseudo-operator by combining several mechanisms String interpolation work not only for arrays but also for dereferencing of arrays. `" @{$a_ref} "` The `[...]` marks an anonymous array-ref. `" @{[ 1, 2, 3 ]} "` Lists can also include code statements to be executed `" @{[ 1, 2, some_code() ]} "` The returned list will be included into the string. `DB<6> p ">>> @{[ 1, 2, time() ]} <<<" >>> 1 2 1680647910 <<< DB<7>` [download] Cheers Rolf _{(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :) Wikisyntax for the Monastery} update added code examples for each step	[reply] [d/l] [select]
Re^5: Check if key exist in hash but not exact match by eyepopslikeamosquito (Archbishop) on Apr 04, 2023 at 22:23 UTC
Definitely adding this to my snippet file! But I've never seen this syntax before. `@{[]}` is the famous Baby Cart Secret Operator. I must say I'm shocked LanX didn't mention his visualization of this operator, namely "a guy with sombrero dragging a sled(ge) uphill" ... which is why he usually refers to it as the Mexican Sledge operator. See also: Secret Operator References	[reply] [d/l]
Re^5: Check if key exist in hash but not exact match by kcott (Archbishop) on Apr 04, 2023 at 22:41 UTC
G'day ibm1620, The `@{[...]}` construct is one of many that are referred to as "Perl secret operators and constants". This one, called "Baby cart", has been around for a very long time. Follow that link for an answer to your question as well as other information. I have been using it since the 1990s and, as I recall, wasn't even aware that it was a perlsecret until much later. I think I first encountered it in one of the "O'Reilly Perl books". I don't remember which one; although, "Advanced Perl Programming" is a likely candidate. Note that's the original edition; "Advanced Perl Programming, 2nd edition" is completely different — a very poor choice of title in my opinion. — Ken	[reply] [d/l]
Re^6: Check if key exist in hash but not exact match by ibm1620 (Hermit) on Apr 05, 2023 at 12:11 UTC
contented sigh I love Perl.	[reply]

update