comment on

Based on your reply, and on these old nodes:

Re: Comparing two hashes-help: "I often find it useful to describe logic like this in terms of a finite-state machine (FSM)"
Re: Spliting file + removing column: "For this, I use “finite-state machine (FSM)” logic"
Re: ADSI groups users: "I naturally look at such problems with an eye toward so-called finite state machine logic"
Re: IO::Socket client does not detect when server network connection dies: "Logic like this is sometimes well designed using Finite State-Machine (FSM) logic"
Wisdom on how to build a "stressful simulation test" with Selenium & POE: "Each actor is basically an individual finite-state machine"
Re: A way to avoid repeated conditional loops: "Call it “a flag variable” if you want to, but this is a classic place for a finite-state machine (FSM) algorithm"
Re: Perl/Tk code structure: "A typical design for the shepherd process is a Finite-State Machine (FSM), or more likely, two FSMs"
Re: how did blocking IO become such a problem?: "The entire life cycle of a request, and much of the outer request-handling heuristics, is most easily described using a finite-state machine (FSM) algorithm"
Re: Clubbing array elements together:: "I prefer to solve such problems using a Finite-State Machine (FSM) algorithm"
Re: File Find/Replace with the replacement coming from part of earlier matched string: "This is an absolutely classic case for a “finite-state machine (FSM)” algorithm"
Re: How to check if successfully logged in?: "it must be a finite-state machine (FSM) design, because in the final analysis the host web-site is driving the bus ... Fact of the matter is, a production mechanize-script is often two FSMs"
Re: Reading concurrently two files with different number of lines: "It might be useful for you to look at the concept of Finite-State Machine (FSM) algorithms as a source of ideas for generalized solutions to these problems"
Re: RFC: Simulating Ruby's "yield" and "blocks" in Perl: "these can be used to implement finite-state machines (FSMs)"
Re: Selecting HL7 Transactions: "this sort of thing is most-easily handled by finite-state machine (FSM) techniques"
Re^2: Too much recursion: "For dealing with very complicated inputs, the notion of a Finite-State Machine (FSM) can be useful"
Re: Sorting through a file with multiple tables and extracting data: "The general approach is that of a finite-state machine (FSM)"
Re: Is this a simple, robust, and maintainable design?: "sounds like a Finite-state machine"
Re: Can I/O operations on the same IO::Socket be executed in different threads?: "That one thread, with simple FSM = Finite-State Machine logic, can keep track of them all"
Re: Algorithm inspiration required. (2018 update): "the aforementioned FSM algorithms might prove to be extremely useful and of course much-preferable" (Buk and YourMum reply)

it appears your manic obsession with finite state machines (FSMs) continues unabated.

I have a suggestion. Instead of making yet another knee-jerk "use a FSM!!!" exhortation to almost any random question, how about giving something useful and lasting to the community, by writing a nice meditation -- along with complete, working, tested code and tests -- describing your favourite and most instructive FSM implementation, from the presumably hundreds you've written during your illustrious career.

Update (2021): SunnyD bothered to log in to give an attaboy to perlfan for suggesting a DFA in Re: Augmenting and reducing data structures.

In reply to Re^2: [Solved]Need to extract a particular block of lines between two patterns by eyepopslikeamosquito
in thread [Solved]Need to extract a particular block of lines between two patterns by chengchl

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.