Re^4: Unable to get the paragraph in the list of hashes. Getting single lines instead.

Hi,

Sorry for the late reply. Just logged in after work. This is awesome!!. Truly a genius solution!!. There's a lot I've learnt from your code.

Just so that I get it right, when you say next if !/^(\d+):(.*)/s; it means, just move next if you find a line that starts with one or more digits, followed by a colon, and then some stuff. I am not sure what the /s does though, does it mean "spill" this regex over even if there is a new line?

Further down, the next if !/^\s*?([^=]+)\s*=\s*(.*)/ I guess means

next if ! -> Move to the next line if the line does NOT
/
^\s*?  -> begin with one or more space (? makes this lazy I guess)
([^=]+)-> Does not include the literal "equal to" sign & create captur
+e group of whatever text is there.
\s* -> Some more space.
= -> Literal "equal to"
\s* -> Some more space.
(.*) -> Second capture group of the remaining stuff.
/
[download]

Please let me know if my understanding is right.

The lines my ($id, $tail) = ($1, $2) and the entire code in the second while loop is simply amazing and an eye opener!! I have no words to express my gratitude for showing this amazing stuff!!

Comment on Re^4: Unable to get the paragraph in the list of hashes. Getting single lines instead. Select or Download Code

Replies are listed 'Best First'.
Re^5: Unable to get the paragraph in the list of hashes. Getting single lines instead. by GrandFather (Saint) on Sep 21, 2020 at 21:05 UTC
`next if !/^(\d+):(.)/s;` skip the remainder of the loop body and start the next itteration - in this case, deal with the next record. The `\s?` isn't actually required at all. The ? does mean "lazy" - match the fewest white space characters possible and still match. See perlre for regular expression documentation. The /s (s at the end of the regex) means treat the string as a single line. That captures the remainder of the record regardless of the line breaks in it. next and last are loop control statements. They skip to the next iteration or terminate the loop respectively. They are very important to understand to help write clear succinct code. Your analysis of the regex is spot on. The regex is not so great though. In particular, both the `\s*` matches could be omitted because they actually do nothing - maybe my coffee levels were dropping by the time I wrote that? Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^5: Unable to get the paragraph in the list of hashes. Getting single lines instead.
by GrandFather (Saint) on Sep 21, 2020 at 21:05 UTC

next if !/^(\d+):(.*)/s; skip the remainder of the loop body and start the next itteration - in this case, deal with the next record.

The \s*? isn't actually required at all. The ? does mean "lazy" - match the fewest white space characters possible and still match. See perlre for regular expression documentation.

The /s (s at the end of the regex) means treat the string as a single line. That captures the remainder of the record regardless of the line breaks in it.

next and last are loop control statements. They skip to the next iteration or terminate the loop respectively. They are very important to understand to help write clear succinct code.

Your analysis of the regex is spot on. The regex is not so great though. In particular, both the \s* matches could be omitted because they actually do nothing - maybe my coffee levels were dropping by the time I wrote that?

Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond

[reply]
[d/l]
[select]