1. Rob: 2.4 upgrade suggestion
Rob:
When working with very large programs that span a large number
of include files it's very difficult to locate the file with the
'Warning' in it:
"Warning: win.ew:378 - statement after return will never be executed"
This works very well: you can find the statement very easily because
the file NAME and LINE NUMBER is given. You open the file, you go to
the line, you edit the statement. Done.
On the other hand:
"Warning: private variable len in Create() is not used"
Ok that's great, but where exactly is the function "Create()" located?
Let me see, did i put it in Win.ew, WinEx.ew, WinEx2.ew, or one of the
other 47 files ??
Would be not only 'nice to see' but much easier to edit if the
warning read something like:
"Warning: Win.ew private variable len in Create() is not used"
I'm currently in the process of upgrading a LOT of programs
from v2.0 to v2.3 & v2.4 and although i use a special file
search program it would be much faster if the warning message
always gave an indication of what file the warning occurred in.
This really cant be that hard to add 
Also, is there any way to output the 'warning' text to a file
instead of the console?
Take care,
Al
2. Re: Rob: 2.4 upgrade suggestion
- Posted by akusaya at gmx.de
Mar 21, 2003
more suggestion:
Sometimes when an error occurs, the
"called from ..." lines is too long, scrolling the window, so I cannot
see the error message itself.
So make it paused (wait for a key) or truncated before the window
scrolls.
Thanks.
A> Rob:
A> When working with very large programs that span a large number
A> of include files it's very difficult to locate the file with the
A> 'Warning' in it:
A> "Warning: win.ew:378 - statement after return will never be executed"
A> This works very well: you can find the statement very easily because
A> the file NAME and LINE NUMBER is given. You open the file, you go to
A> the line, you edit the statement. Done.
A> On the other hand:
A> "Warning: private variable len in Create() is not used"
A> Ok that's great, but where exactly is the function "Create()" located?
A> Let me see, did i put it in Win.ew, WinEx.ew, WinEx2.ew, or one of the
A> other 47 files ??
A> Would be not only 'nice to see' but much easier to edit if the
A> warning read something like:
A> "Warning: Win.ew private variable len in Create() is not used"
A> I'm currently in the process of upgrading a LOT of programs
A> from v2.0 to v2.3 & v2.4 and although i use a special file
A> search program it would be much faster if the warning message
A> always gave an indication of what file the warning occurred in.
A> This really cant be that hard to add
A> Also, is there any way to output the 'warning' text to a file
A> instead of the console?
A> Take care,
A> Al
A> TOPICA - Start your own email discussion group. FREE!
3. Re: Rob: 2.4 upgrade suggestion
akusaya at gmx.de wrote:
> Sometimes when an error occurs, the
> "called from ..." lines is too long, scrolling the window, so I cannot
> see the error message itself.
>
> So make it paused (wait for a key) or truncated before the window
> scrolls.
You can always look in ex.err to see everything.
What's on the screen is a small subset of what's in ex.err.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
4. Re: Rob: 2.4 upgrade suggestion
Al Getz wrote:
> On the other hand:
>
> "Warning: private variable len in Create() is not used"
>
> Ok that's great, but where exactly is the function "Create()"
located?
> Let me see, did i put it in Win.ew, WinEx.ew, WinEx2.ew, or
one of the
> other 47 files ??
OK, I'll look into it.
> Also, is there any way to output the 'warning' text to a file
> instead of the console?
No there isn't, (maybe in Linux you could redirect stderr)
but I'll consider it.
Maybe, at least, if an ex.err is going to be generated
I could dump any warnings in there as well.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
