Re: [mh] Error Reporting for Malformed User Code

[Joel D. <jr...@pr...>]

Eloy,

I'm thinking that if we can track the order in which the files
are concatenated, and we know how many lines are in each one,
it should be easy to calculate which line of which file the error
occurred in based on the line number that mh is currently returning.

Joel


On Tue, 22 Jan 2013, it would appear that Eloy Paris wrote:

> Hi Joel,
>
> On 01/22/2013 02:40 PM, Joel Davidson wrote:
>
>> One thing I'd like to see in the console printout is for the source of
>> the error to be more accurately indicated.
>> 
>> Currently the line number relates to the mh_temp.user_code file,
>> which is is a concatenation of all of the active source files.
>> It would be nice if when this file was created the size and order
>> of the source files was logged someplace so the actual file/line
>> number of the error could be indicated.
>
> Yeah, that'd be indeed nice. Not sure something like this already exists.
>
>> I haven't had the time to look into where the mh_temp.user_code
>> file is created, but I don't think it should be that difficult
>> to add this capability.
>
> mh_temp.user is created in the data directory, i.e. "data_dir" in the .ini 
> file.
>
> I think the problem with accurately reporting the name of the file and the 
> line number where an error exists is that all files are evaluated at once via 
> mh_temp.user_code, so it really is not possible to accurately pinpoint the 
> exact file and line number. I am not 100% how this part works, though.
>
> Cheers,
>
> Eloy Paris.-
>