Skip to main content



      Home
Home » Language IDEs » Java Development Tools (JDT) » feature request/proposal
feature request/proposal [message #59716] Tue, 17 June 2003 16:50 Go to next message
Eclipse UserFriend
Hi, all:

i look at the source code of my java file, quite big percentage of it
is logging codes (either use Log4j or System.println). and they made the
code less readable. and, during the debug process, thoese statements are
commented on/off back and force again and again.

i just imagine if our Java editor could have such a feature:

o The source editor produce a look-up table of all log statements inside
each classes/methods;
o There is a check box for each statement/method/class to turn on/off;
o When we doing editing, we can optionally turn on/off those log
statements to be displayed or not in the source file;
o Before summit to compilor, the editor strip off all un-checked
statement and only keeps the checked; so that we only produce
output
for the places we wanted.

thank you for your attention.

best regards.

kevin.
Re: feature request/proposal [message #59740 is a reply to message #59716] Tue, 17 June 2003 16:58 Go to previous messageGo to next message
Eclipse UserFriend
> i look at the source code of my java file, quite big percentage of it
> is logging codes (either use Log4j or System.println). and they made the
> code less readable. and, during the debug process, thoese statements are
> commented on/off back and force again and again.

You could look at AspectJ (http://www.eclipse.org/ajdt/), which lets you
factor out logging and other features ("concerns") that appear in fixed
places in your code, e.g. the beginning and end of every method. It's
pretty powerful, though I haven't totally gotten my head around it yet.
But it's also a new programming language that extends Java quite a
bit, so your code wouldn't really be Java any more.

Laura
Re: feature request/proposal [message #59969 is a reply to message #59716] Wed, 18 June 2003 02:50 Go to previous message
Eclipse UserFriend
Originally posted by: yves.somewhere.com

Instead of printing the values you want, run your application in
debugging mode in Eclipse, and put breakpoints at the places where
you want to verify the value of a variable.

You can enable / disable breakpoints so you only stop at the
places where you want.


kevin wrote:
> Hi, all:
>
> i look at the source code of my java file, quite big percentage of it
> is logging codes (either use Log4j or System.println). and they made the
> code less readable. and, during the debug process, thoese statements are
> commented on/off back and force again and again.
>
> i just imagine if our Java editor could have such a feature:
>
> o The source editor produce a look-up table of all log statements inside
> each classes/methods;
> o There is a check box for each statement/method/class to turn on/off;
> o When we doing editing, we can optionally turn on/off those log
> statements to be displayed or not in the source file;
> o Before summit to compilor, the editor strip off all un-checked
> statement and only keeps the checked; so that we only produce
> output
> for the places we wanted.
>
> thank you for your attention.
>
> best regards.
>
> kevin.
>
>
Previous Topic:Eclipse Debugger Prespective Without Any other Prespective
Next Topic:Unknown warnings
Goto Forum:
  


Current Time: Sun Jun 01 00:02:58 EDT 2025

Powered by FUDForum. Page generated in 0.03150 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top