1. Debug Information

Sometime ago I made a program, binded it, and sent it to one of my
friend. Then he said that my program wasn't working because it
outputted an error "name for dir() is too long".

I don't know where it is and I needed to send him another version
which I have put lines like this:

 fOut = open("c:\\debug.txt", "a")
 procedure debug(object st)
    puts(fOut, st & "\n")
 end procedure
 ...
 debug("<file.e> procName path=" & path)
 dir(path)
 ...
 debug("<other.e> otherProcName file=" & file)
 dir(file)

 etc... at every line which has "dir()"
 
 
I thought it would be nice if the bind program can have an option to
add debug information so if an error happens, it can output such things:

 name for dir() is too long
 was at: c:\project\something\file.e line 123

then output the usual error report to ex.err.

(instead of
 name for dir() is too long
 d:\PROGRAM.EXE line 90000 <-- because it is already binded)

        - - -
 
More suggestion: add a display for where the ex.err file is.
example:

 slice length is not same
 See c:\abc\ex.err <-- full path!

because when I asked for the ex.err file to a friend, he asked
"where is the ex.err file?"


I hope (especially for the latest thing, because it's simpler) it can
be added to next eu release. It is needed for faster development.

Thanks!

new topic     » topic index » view message » categorize

2. Re: Debug Information

aku saya wrote:
> Sometime ago I made a program, binded it, and sent it to one of my
> friend. Then he said that my program wasn't working because it
> outputted an error "name for dir() is too long".

The file path was over 255 characters.

> I thought it would be nice if the bind program can have an option to
> add debug information so if an error happens, it can output such things:
> 
>  name for dir() is too long
>  was at: c:\project\something\file.e line 123
> 
> then output the usual error report to ex.err.
> 
> (instead of
>  name for dir() is too long
>  d:\PROGRAM.EXE line 90000 <-- because it is already binded)
> 
>         - - -
>  
> More suggestion: add a display for where the ex.err file is.
> example:
> 
>  slice length is not same
>  See c:\abc\ex.err <-- full path!
> 
> because when I asked for the ex.err file to a friend, he asked
> "where is the ex.err file?"

OK, thanks.
I'll add these ideas to my suggestions folder.

Regards,
    Rob Craig
    Rapid Deployment Software
    http://www.RapidEuphoria.com

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu