close Warning: Can't synchronize with repository "(default)" (/var/svn/tolp does not appear to be a Subversion repository.). Look in the Trac log for more information.

Opened 19 years ago

Closed 16 years ago

#433 closed defect (fixed)

compile & decompile

Reported by: giken019 Owned by: Jorge
Priority: highest Milestone:
Component: Interface Version: head
Severity: blocker Keywords:
Cc:

Description

I noticed that a variable that has been compiled and decompiled sometimes cannot be compiled again.

For example, if I create a timeset and see the calendar by clicking on "Ver conjunto temporal" and decompile the timeset without closing the calendar :

TimeSet a = WD(7)

and compile it again, I get the message :

ERROR: [2] Conflicto entre variables.
Se ha intentado modificar "a" a través de la variable "a"

This bug IS NOT only occurring with TimeSet because later I have noticed the same kind of bug with Sets of Texts although I cannot identify a sequence.

I think that this kind of bug can also occurs when there is an error of some kind at the moment of compiling. If for example the grammar is wrong (forget a ; sign), at some point the compiling and decompiling problem appears.

Change History (6)

comment:1 Changed 19 years ago by Víctor de Buen Remiro

I think that the best solution would be not to allow to decompile any file while there are objects in use in Eval window or all those that introduce references to TOL objects.

It could be asked the user if it wishes to clean those windows and to continue with the file decompilation, or it wishes to cancel it, in order to verify if there is something the user wants to conserve.

comment:2 Changed 18 years ago by Jorge

Owner: changed from rcsoto to Jorge

checking the bug ....

comment:3 Changed 18 years ago by Jorge

Status: newassigned

The bug is still around. The reason is that when exploring a timeset the reference count is incremented. When the calendar explorer is closed then the reference count is decremented but nothing is done about checking if that object should died because nobody will reference it.

One solution could be trying to DESTROY the object from the calendar explorer.

Another solution could be disallow decompiling the object from the console if they are referenced by other containers.

Any other idea?

comment:4 Changed 18 years ago by Víctor de Buen Remiro

I think that TOLBase should disallow decompiling a file that is already referenced. Probably it will be easier to implement if internal class BSetFromFile and related ones support this feature.

comment:5 Changed 18 years ago by Jorge

bug_file_loc: http://cvs.tol-project.org/viewcvs.cgi/tol_tests/toltcl/Bugzilla/bug_000433

Yes, I think checking if a file could be decompiled or not is better done inside TOL, may be for next release (not in 1.1.5)

Now in console if an object is referenced by other "component" then it will not be released.

We are doing some other checks before closing this bugs.

Also there is a test implemented at http://cvs.tol-project.org/viewcvs.cgi/tol_tests/toltcl/Bugzilla/bug_000433

any other comments?

comment:6 Changed 16 years ago by Víctor de Buen Remiro

Component: VariousInterface
Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.