Proceedings of 1996 Australian Software Engineering Conference
DOI: 10.1109/aswec.1996.534121
|View full text |Cite
|
Sign up to set email alerts
|

Automatic analysis of functional program style

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
9
0

Publication Types

Select...
5
3

Relationship

0
8

Authors

Journals

citations
Cited by 13 publications
(9 citation statements)
references
References 16 publications
0
9
0
Order By: Relevance
“…It can be done by hand, but as expected, it will inherit all the problems created by manual checking. Thanks to [14] , as we can execute automata diagram using JFALP. However, for one particular problem, we can have many forms of automata diagrams.…”
Section: Automata-based Assignmentmentioning
confidence: 99%
“…It can be done by hand, but as expected, it will inherit all the problems created by manual checking. Thanks to [14] , as we can execute automata diagram using JFALP. However, for one particular problem, we can have many forms of automata diagrams.…”
Section: Automata-based Assignmentmentioning
confidence: 99%
“…In the 1970's and early 1980's the focus moved away from correctness to optimality assessment (Michaelson, 1996). Since then, there has been renewed interest in automatic correctness assessment.…”
Section: Automatic Correctness Assessmentmentioning
confidence: 99%
“…Metrics, such as line of code, number of variables, statements and expressions, are used as the basis for grading a program. Examples of such systems are STYLE [14,15], Knots [16], style checker [17], Verilog Logiscope [18], Style++ [19]. The advantage of using metrics is that they are easy to calculate.…”
Section: Introductionmentioning
confidence: 98%