Hi Dimiter,

> Tom, I do it with search and repalce (it's pretty safe :)

... as safe as using search and replace for renaming a
class/method/field.

Tom


On Tue, 30 Jul 2002 12:41:49 +0300, "dimiter" <[EMAIL PROTECTED]>
wrote:

> Sometimes you get enormous block of constants and much shorter body of a
> class , and all these long names cause you verbosity-blindness.
> 
> Tom, I do it with search and repalce (it's pretty safe :)
> 
> -- dimiter
> 
> "Pete Hendry" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > Just curious. Why would you want to do this? The compiler puts the
> > constant value in place of the constant "variable" so there is no
> > performance gain.
> >
> > What you appear to want is that YES is like a #def in C/C++ and is
> > inlined. This is not necessary in Java.
> >
> > Pete
> >
> > Oh yeah, -1 :-)
> >
> > Thomas Singer wrote:
> >
> > > Since months, I would like to have the option to inline constants --
> > > simply replacing their usage with their initialisation...
> > >
> > > Example:
> > >
> > > public static final Option YES = Option.YES;
> > >
> > > ...
> > >   setOption(YES);
> > > ...
> > >
> > > ==>
> > >
> > > ...
> > >   setOption(Option.YES);
> > > ...
> > >
> > > I know, I can do it with cut'n'paste, but I'm able to do each
> > > refactoring with the help of cut'n'paste.
> > >
> > > Tom
> > >
> >
> 
> 

_______________________________________________
Eap-features mailing list
[EMAIL PROTECTED]
http://lists.jetbrains.com/mailman/listinfo/eap-features

Reply via email to