search

ARudik / phc

Automatically exported from code.google.com/p/phc
0 stars 0 forks source link

Potential warnings and errors #98

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
This issue is just a dumping ground for future warnings and errors that phc
should define (it is marked optimization since analysis is typically
required for these errors/warnings).

- nested class definitions
- Either no, or all, method paths should return a value, not some.
- Using the result of a function which doesnt return a value

Original issue reported on code.google.com by paul.biggar on 16 Nov 2008 at 11:39

GoogleCodeExporter commented 9 years ago 
- multiple definitions of the same function/class/interface

Original comment by paul.biggar on 17 Nov 2008 at 12:26