Hello,
when I compile script, even with verbosity =0 I meet plenty of messages like
error operator * <10LinearCombI7MGauche4C_F0E>, <10LinearCombI7MGauche4C_F0E>
Where is a documentation allowing to understand these messages ?
JLuc
Hello,
when I compile script, even with verbosity =0 I meet plenty of messages like
error operator * <10LinearCombI7MGauche4C_F0E>, <10LinearCombI7MGauche4C_F0E>
Where is a documentation allowing to understand these messages ?
JLuc
Hello,
There is no documentation on such error messages. Here it indicates that an expression you write is invalid. In the output message you should have the line number refering to your code. You have to check this line, and look at some examples in order to understand how to write a correct form.
Thanks for your reply.
Then I must conclude that all such messages resulting from the compiler -even when verbosity=0- are useless ?
It shocks my logic sense of view. Also, it is not written in assembler, some language convention seems to be.
Any else could interact with developers ?
Regards
JLuc
verbosity is used to ajust the level of information you get during normal execution. It does not concern error messages. Error messages are emitted when the compilation or execution interrupts for some fatal reason. They are not useles: they help you to find the mistake in the code and correct it, even though they can be understood in detail only by FreeFem developers. The error message you have is from the interpreter of FreeFem code lines. Since it says it concerns “linear combination”, it means that a product in your formula is not correct, maybe you are multiplying two objects that cannot be multiplied, or your variational formulation is not linear with respect to the test function or the unknown, or something similar.
Never think about this, but i don’t think it is a good idea.
Of course, first line(s) of compiler mentions the locus of my error, it is not the topic of my question.
I did not join the following of such an error message, but there was a plain page of “alternative solution” with incomprehensible lines.
So if it is only exploitable by code developers, as Frederic Hecht says, it brings the answer I was searching for. However, surfing on the net with IA seems to show that these lines are interpretable
I regret that we can’t have access to the explanation of compiler lines, it could facilitate some intricate errors, when trivial one are exclude.
I think, I will try an add a layer to clarify this output, because today , it just gives C++ type name, it is difficult an understand event for me.