id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
2133	OMEdit: Handling multiple class definitions in one file	Per Östlund	somebody	"OMEdit allows the user to open a file that contains multiple class definitions, e.g. a file that contains:
{{{
model A end A;
model B end B;
}}}
Opening such a file simply adds the classes to the top scope. However, if you open one of the classes and save it, then OMEdit overwrites the file and saves only that class. This means that the other classes in the file are lost.

The specification says this however (section 13.2.2.2):
>A nonstructured entity [e.g. the file A.mo] shall contain only a stored-definition that defines a class [A] with a name matching the name of the nonstructured entity.
So defining multiple top-level classes in one file is not really allowed, even though both OM and Dymola allows it.

So we should either forbid it completely (but tell the user why), or make sure that OMEdit saves all models in the file."	defect	closed	high	1.9.0	Interactive Environment	trunk	duplicate