DOI: 10.1007/978-3-540-74240-1_24
|View full text |Cite
|
Sign up to set email alerts
|

Productivity of Stream Definitions

Abstract: We give an algorithm for deciding productivity of a large and natural class of recursive stream definitions. A stream definition is called 'productive' if it can be evaluated continuously in such a way that a uniquely determined stream is obtained as the limit. Whereas productivity is undecidable for stream definitions in general, we show that it can be decided for 'pure' stream definitions. For every pure stream definition the process of its evaluation can be modelled by the dataflow of abstract stream elemen… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
43
0

Publication Types

Select...
7
2

Relationship

2
7

Authors

Journals

citations
Cited by 26 publications
(43 citation statements)
references
References 11 publications
0
43
0
Order By: Relevance
“…The notion of productivity given in [14,42] is equivalent to our notion of weak normalisation. The notion of productivity is defined as weak normalisation but excluding terms that do not contain constructors such as (tl (tl (tl .…”
Section: Conclusion and Related Workmentioning
confidence: 99%
“…The notion of productivity given in [14,42] is equivalent to our notion of weak normalisation. The notion of productivity is defined as weak normalisation but excluding terms that do not contain constructors such as (tl (tl (tl .…”
Section: Conclusion and Related Workmentioning
confidence: 99%
“…Productive streams are defined in the literature [6] as terms weakly normalizing to infinite lists, which is in our case equivalent to: a stream s is productive if for all n :: Nat, s !! n evaluates to a strict value.…”
Section: Lemmamentioning
confidence: 99%
“…The start language S can be specified by providing a tree automaton T that generates S; the program then searches an extension of T which fulfills the requirements of Theorem 6.3. Note that with the productivity tool of [3] we could already prove productivity of this specification fully automatically. a(b(c)))), and 2 < 3.…”
Section: Examples and Toolmentioning
confidence: 99%