[TEC 3.9] Fewer large baroc files vs. many small baroc files?

Hallo,


>restructuring my baroc files so that I have a separate file for each 
event class
>in fact, after compile/load, you can delete the entire TEC_CLASSES 
directory(s)
> and TEC does not seem to notice until the next time you compile/load).

yes, but try to delete $DBDIR/tec/rb_dir/TEC_CLASSES and be surprised when 
restarting ;)

TEC parses the files on startup and inserts all classes in TEC_T_ISA
with their parent/child relationship, so the files are definitely 
required.
I think your approach would work, but imagine 5000-15000 files in a 
directory.
This is quite some overhead for the OS, and imagine the upgrade fun
when *any* product changes its classes. You'd have to identify which
class has changed, or simply decompose the files from the upgrade
and reapply your changes -- imho a nightmare.

I'd vote for keeping the files as-is (as-are? ;) ) and decompose using a 
BNF parser
when you need it.

Nice idea to include baroc source with the "information" button ;).

Tschau...Thomas
-- 
"Do you wanna be a legend or a passing footprint on the sands of time?"

Senior Consultant, Tivoli Certified Enterprise Consultant + Instructor
santix AG, www.santix.de, info-/JKUMw0Y9jazQB+pC5nmwQ@xxxxxxxxxxxxxxxx, fon 
+49-89-321506-0, fax -99
Weihenstephaner Str. 4, D-85716 Unterschleissheim, GSM +49-170-9135811