Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-VerveineJ
New issue 1030 by anquetil...@gmail.com: VerveineJ does not export local variables http://code.google.com/p/moose-technology/issues/detail?id=1030
Some local variables are not exported in the mse file even when we don't specify the -summary option
Updates: Status: Fixed
Comment #1 on issue 1030 by anquetil...@gmail.com: VerveineJ does not export local variables http://code.google.com/p/moose-technology/issues/detail?id=1030
Local variables with primitive type are not exported by default Added an option -alllocals
Comment #2 on issue 1030 by tu...@tudorgirba.com: VerveineJ does not export local variables http://code.google.com/p/moose-technology/issues/detail?id=1030
Why are they not exported by default?
Comment #3 on issue 1030 by anquetil...@gmail.com: VerveineJ does not export local variables http://code.google.com/p/moose-technology/issues/detail?id=1030
1- save space 2- There is an assumption that local variables in methods are mainly interesting when they indicate use of another class. If we consider 2 for loops: - for (int i=0; i < 100; i++) We are probably not interested in the i local variable - for (SomeClass o : aCollection) It is probably more interesting to know about the o local variable
nicolas
-
moose-technology＠googlecode.com