LogMsg bug?

[johansamuelsson]

Hi

I have two files

c:\temp\p1.prg

Code: Select all

LogMode(name="logg") LogMsg LogMsg 11 Exec c:\temp\p2.prg LogMsg 12

and c:\temp\p2.prg

Code: Select all

LogMsg TEST

When running p1.prg Eviews ouput (in the log) is

11
12

I expected

11
TEST
12

Or am I wrong?

Regards Johan

[EViews Katerina]

If your p1 was :

LogMode(name="logg") LogMsg
LogMsg 11
include c:\temp\p2.prg
LogMsg 12

Then the output in the log window would be:
11
TEST
12

The exec command executes another program. The include statement includes the contents of another file in a program file.

Using the exec command you need to add logmode to your second program ;

logmode l
LogMsg TEST

then a second log would open and display
TEST

[johansamuelsson]

Ok, thanks

Regards Johan

[linkan]

The prg-files Johan showed worked up until the most recent patch, in witch this behaviour was removed. Is there a reason that it is removed?

[EViews Katerina]

We have an internal discussion about the issue. We will update you once is resolved.

[EViews Katerina]

With the latest patch we reverted to previous behavior of EViews10 for logging program messages when exec command is used inside a program:

p1.prg :
LogMode l
LogMsg 11
exec p2.prg
LogMsg 12

p2.prg:
LogMsg TEST

Then the output in the log window would be:
11
TEST
12

EViews11 behavior is changed and the program that is being executed with exec command will require a LogMode command and log messages will be displayed in a new dialog as described in previous post.

[linkan]

EViews11 behavior is changed and the program that is being executed with exec command will require a LogMode command and log messages will be displayed in a new dialog as described in previous post.

Why is this change implemented in Eviews 11? It feels strictly worse than the Eviews 10 behaviour. At least it should be possible to get the old behaviour with a Logmode option.

[tvonbrasch]

Hi

Have you done anything with this logmsg-issue?
t