Timeline
2014-03-01:
- 08:07 Ticket #2606 (Backend - Bad equation solving (wrong symbolic manipulation)) closed by
- invalid: damn, is this damn cold :)
- 07:55 Ticket #2606 (Backend - Bad equation solving (wrong symbolic manipulation)) updated by
- Replying to adrpo: > a = c - bc + bd multiply c with (1 …
- 07:49 Ticket #2606 (Backend - Bad equation solving (wrong symbolic manipulation)) updated by
- I would say no: […]
- 07:43 Ticket #2606 (Backend - Bad equation solving (wrong symbolic manipulation)) updated by
- Well... Isn't it actually correct? […]
- 07:40 Ticket #2606 (Backend - Bad equation solving (wrong symbolic manipulation)) updated by
- Seems that: […]
- 07:39 Ticket #2606 (Backend - Bad equation solving (wrong symbolic manipulation)) updated by
- […] Gives […]
- 06:05 Ticket #2606 (Backend - Bad equation solving (wrong symbolic manipulation)) updated by
-
Cc changed
Question: can we look with the debugger at the solving process to see … - 06:01 Ticket #2606 (Backend - Bad equation solving (wrong symbolic manipulation)) created by
- Solving this system of equations: […] for b should result in: …
- 03:56 Ticket #2605 (Backend - Can MathML blocks be nested in the XML dump?) updated by
- I think you can commit it as you're the only one using dumpXMLDAE as …
- 03:52 Ticket #2605 (Backend - Can MathML blocks be nested in the XML dump?) created by
- Matt and I were looking at the XMLDump code this afternoon, and we …
2014-02-28:
- 10:50 Ticket #2344 (OMEdit - Erroneous display of two MSL 3.2.1. components) updated by
- I did my checks with r19013. I repeated today with r 19348 and I got …
2014-02-27:
- 20:01 Ticket #2344 (OMEdit - Erroneous display of two MSL 3.2.1. components) updated by
- What do you mean by Erroneous display? The bug is probably already fix …
- 16:27 Ticket #2344 (OMEdit - Erroneous display of two MSL 3.2.1. components) updated by
-
Priority changed
- 16:26 Ticket #2344 (OMEdit - Erroneous display of two MSL 3.2.1. components) updated by
- I've found other cases of graphical misbehaviour of OMEdit. Naturally …
2014-02-26:
- 21:41 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) closed by
- fixed: Fixed in r19323.
- 21:41 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
-
Status, Owner changed
- 21:38 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Yep. The unwarranted assumption was that appropriate quoting would …
- 21:25 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Replying to janssen: > But if this function is being …
- 21:23 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- I think old-world Mac just used CR, anyway.
- 21:22 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- You think it would run on old-world Mac? It probably should just …
- 21:20 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Replying to janssen: > There is no world in which \n …
- 20:59 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Replying to lochel: > I don't get the both else cases. I …
- 20:57 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- The nl flag comes from above to tell this function to either escape or …
- 20:50 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- I don't get the both else cases. I would just leave them out - but I …
- 20:47 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- There is no world in which \n followed by \r is a newline, so the case …
- 20:43 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- What's this nl flag doing, and what code generates it?
- 20:38 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- I guess not too many unwarranted assumptions as this would have been …
- 20:33 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- I guess that's one way to look at it. But it seems that the code …
- 20:26 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- I asked sjoelund.se to have a look at this. Seems is working if …
- 20:23 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- I use omc on the command-line to generate the simulation code, then …
- 20:22 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Sorry, I should have said I was using a Unix machine. A Snow Leopard …
- 20:07 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Ok. You're right. Seems I can reproduce this on Linux.
- 19:58 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Ouch. Sorry about the config.log. How do you try to build the model? …
- 19:39 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Checked out an update, and rebuilt. Same problem. <Gripe> "make …
- 19:37 Ticket #2604 (Frontend - setState__pTX error using different Media (Modelica.Fluid and ...) updated by
- A workaround for now is this: […] A fix for this is in the …
- 19:33 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Well, my OM is from last week's sources :-). I'll update and rebuild.
- 19:28 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Just for posterity, I tested with r19322 and compilation works fine.
- 19:22 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Seems the error comes from MSL Media PartialMedium or all the other …
- 19:18 Ticket #2604 (Frontend - setState__pTX error using different Media (Modelica.Fluid and ...) updated by
- Hi, This is a known bug and a fix is on the way. Mostly because we …
- 19:15 Ticket #2604 (Frontend - setState__pTX error using different Media (Modelica.Fluid and ...) created by
- Using OM 1.9.1+dev (r18571) If you are using not only one Medium but …
- 19:04 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- I got an email from janssen which (non public) model has this issue. …
- 19:00 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Which is why we have code that escapes string literals... I would …
- 18:41 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
-
Status changed
- 18:27 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Traced this back to an assert statement in the library I'm using. It …
- 18:12 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) created by
- My generated simulation code doesn't compile, because of constructs …
- 11:26 Ticket #2602 (Frontend - Handle function default arguments better) created by
- We need to handle function default arguments better. Either by saying …
2014-02-25:
- 04:42 Ticket #2565 (New Instantiation - Problems with code generation - package constants in ExternalMedia) updated by
- Bug #2412 (with the IncludeDirectory/LibraryDirectory) is now fixed. …
- 04:40 Ticket #2412 (Frontend - Include and Library annotations for external function do not work when ...) closed by
- fixed: Fixed in r19290.
2014-02-24:
- 08:38 Ticket #2593 (OMNotebook - Examples not defined properly) closed by
- fixed: That seems reasonable, fixed in r19272.
Note:
See TracTimeline
for information about the timeline view.
