Opened 11 years ago

Closed 9 years ago

#2439 closed defect (duplicate)

Merge parts of the minimal unparsing branch into master

Reported by: Adrian Pop Owned by: Adrian Pop
Priority: high Milestone: 1.9.3
Component: Interactive Environment Version: trunk
Keywords: Cc:

Description

Currently we do not have any buffers for the
strings we sent to OMC from OMEdit or other
clients.

Also, list() command does not display the actual buffers
but the unparsing of Absyn.Program which will move comments
and remove formatting. In the minimal unparsing branch we
have already added a new API called listBuffer which will
use the actual buffer when unparsing a program. This part
should be in the trunk/.

Change History (8)

comment:1 by Adrian Pop, 11 years ago

Owner: changed from somebody to Adrian Pop
Status: newaccepted

comment:2 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:3 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:4 by anonymous, 10 years ago

Could this be solved in the near future? It makes writing own codes in OMEdit a real pain!

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

Summary: Merge parts of the minimal unparsing branch into trunk/Merge parts of the minimal unparsing branch into master

I think it should be possible to do an unparsing that simply merges the old file with the new information; then buffers would not be needed and the API functions would not need to consider how to unparse the data (otherwise new API functions may break things, I guess).

comment:6 by anonymous, 9 years ago

Anything new here?

comment:7 by Adrian Pop, 9 years ago

We did some more work on this in ticket #2905 but we still have some work to do to finish it.

comment:8 by Adrian Pop, 9 years ago

Resolution: duplicate
Status: acceptedclosed

I'll close this ticket as we're working on #2905 now.

Note: See TracTickets for help on using tickets.