Attached is the background material related to Inovys's submission to P1450.4 for flow control (Inovys calls its language "Stylus"). I'm not aware of any e-mail reflector for the working group - I'll be happy to post this if you tell me how.

The attached material includes a) the syntax to a very simple STIL program (OddEven.stil), b) a UML static structure diagram that roughly corresponds to the diagram on page 2 of the P1450.4 document (StylusSubmission.jpg). Below is an HTML table that helps to map between the P1450.4 names and the names in Stylus.

I should state the standard disclaimer, that this material remains property of Inovys until it is incorporated into the 1450 standard. Until then, it is intended for review only by the working group members and for purposes only related to determine its suitability for incorporation into the standard.

P1450.4 page 2	Stylus	Comments
TestProgram	(unnamed)	Each has 5 entry points, but the names and functionality might be somewhat different: Stylus: TestButton executes Start, then Main, then Finish
Flow	Sequence	Semantically very similar - represents a flow-chart
Node	(unnamed or Segment)	Each represents a specific instance of a shape in a flow-chart, controls sequencing to the next Node.
Bin	Bin	the same - identifies "software bins" each with a counter
BinMap	(not shown)	the same - maps from the software bins to hardware bins (may be handler specific)
Test	Segment	Similar - represents the testing to occur at a "Node". Stylus allows each Segment to call multiple TestMethods, while the P1450.4 allows only a single TestMethod call per Node.
	Branch	Can be handled via a Test without a TestMethod in P1450.4
PatternBurst, Timing, DCLevels, Selector, Plot, Axis , Category	(not shown)	similar

-----------------------------------------------------------------
Don Organ Inovys Corporation
(925) 924-9110 x122
-----------------------------------------------------------------