[FlopCpp-tickets] Re: [FlopC++] #10: Alter the method for generation of the "display()" methods

[FlopC++]

#10: Alter the method for generation of the "display()" methods
-------------------------+--------------------------------------------------
 Reporter:  hpwalton     |        Owner:  hpwalton
     Type:  enhancement  |       Status:  new     
 Priority:  low          |    Milestone:          
Component:  component1   |      Version:          
 Severity:  normal       |   Resolution:          
 Keywords:               |  
-------------------------+--------------------------------------------------
Comment (by thh):

 Definetely enhancement is this area are desirable.

 The existing display method are meant as shortcuts to generate some
 standard output of the optimal value of variable and constraints(dual
 vars). [Improovable]
 But of course there are other things you might want to display.

 It is not clear to me what kind of output you envisage to get from
 toMathML() or cout<<model ? a)The symbolic model? b)The generated
 instance? c)Solution? d) some kind of debud info?

 a) being a modelling language, the code is the model and no translation
 should be required.
 b) MPS is always possible. At a first glance of CoinModel it seems to me
 that we can use it to get a more readable output of the model

-- 
Ticket URL: <https://projects.coin-or.org/FlopC++/ticket/10>
FlopC++ <http://example.com/>
My example project