Issue 1030 in moose-technology: VerveineJ does not export local variables

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 1030 in moose-technology: VerveineJ does not export local variables

moose-technology
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-VerveineJ

New issue 1030 by [hidden email]: 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

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 1030 in moose-technology: VerveineJ does not export local variables

moose-technology
Updates:
        Status: Fixed

Comment #1 on issue 1030 by [hidden email]: 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

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 1030 in moose-technology: VerveineJ does not export local variables

moose-technology

Comment #2 on issue 1030 by [hidden email]: VerveineJ does not export  
local variables
http://code.google.com/p/moose-technology/issues/detail?id=1030

Why are they not exported by default?

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 1030 in moose-technology: VerveineJ does not export local variables

moose-technology

Comment #3 on issue 1030 by [hidden email]: 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

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev