http://bugzilla.lysator.liu.se/show_bug.cgi?id=1180
Summary: Let the Expectable define new actions Product: pcl-expect Version: (cvs) Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: other AssignedTo: ceder@lysator.liu.se ReportedBy: ceder@lysator.liu.se QAContact: pcl-expect-qa@lists.lysator.liu.se
With the current API, the Controller class defines which actions that are available:
- re - eof - timeout
It would be better if the actions could be decoupled from the Controller object. Some actions are only relevant for certain Expectable subclasses. For instance, a hypotetical TcpServer class would probably support a single action: "accept". It would set an attribute to the newly accepted TCP connection (which would probably be a TcpBase object).
Other actions, such as "glob" or "ex"/"exact", could be implemented in terms of the re action (or some sort of generic "match" action).
In order to implement "interact" semantics, where no input is passed to the process until it is certain that it cannot match a previous pattern, all patterns for a particular Expectable must probably know about each other. This complicates things even further.
------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.