Opened 11 years ago

Last modified 7 years ago

#2420 new defect

Do not return error messages when calling checkModel (maybe there are other API that do this)

Reported by: Adrian Pop Owned by: somebody
Priority: high Milestone: Future
Component: Frontend Version: trunk
Keywords: Cc:

Description

Currently checkModel puts the error messages in the string returned.

Should make checkModel return an
array with succes(true)/failure(false) and
the actual message. Then the user can call
getErrorString() to get the error messages.

checkModel -> {true|false, "message"}
getErrorString();

Change History (12)

comment:1 by Martin Sjölund, 11 years ago

Not an array. What the hell? Come on, a tuple (multiple outputs)...

Last edited 11 years ago by Martin Sjölund (previous) (diff)

comment:2 by Adrian Pop, 11 years ago

can OMEdit parse tuples?

comment:3 by Martin Sjölund, 11 years ago

Does the pope shit in the woods? Yes.

comment:4 by Martin Sjölund, 11 years ago

Anyway, OMEdit doesn't need to parse it. Can just do:

(a,b) := checkModel(...);
a;
b;

As 3 commands and parse only the last 2. It does similar things for something else.

comment:5 by Martin Sjölund, 10 years ago

Milestone: 1.9.11.9.2

This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).

comment:6 by Martin Sjölund, 10 years ago

Milestone: 1.9.21.9.3

Milestone changed to 1.9.3 since 1.9.2 was released.

comment:7 by Martin Sjölund, 9 years ago

Milestone: 1.9.31.9.4

Moved to new milestone 1.9.4

comment:8 by Martin Sjölund, 9 years ago

Milestone: 1.9.41.9.5

Milestone pushed to 1.9.5

comment:9 by Martin Sjölund, 9 years ago

Milestone: 1.9.51.10.0

Milestone renamed

comment:10 by Martin Sjölund, 8 years ago

Milestone: 1.10.01.11.0

Ticket retargeted after milestone closed

comment:11 by Martin Sjölund, 8 years ago

Milestone: 1.11.01.12.0

Milestone moved to 1.12.0 due to 1.11.0 already being released.

comment:12 by Francesco Casella, 7 years ago

Milestone: 1.12.0Future

The milestone of this ticket has been reassigned to "Future".

If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.

If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".

In both cases, a short informative comment would be welcome.

Note: See TracTickets for help on using tickets.