How to handle feature located code ...

[marten]

When looking at VAST 6.01 under OS/2 (eCS 2.0) and VASmalltalk 7.5 I noticed, that the (Load/Unload) feature stuff was located (much, much earlier - before 5.0) in subdirectories (e.g. feature), where the control file and the dat file were located.

Actually I was only reading the 4.0 documentation. How is the feature stuff handled since 5.0 ? Is there any documentation available ?

Marten

[wembley]

Marten -

Everything is now shipped in the single repository, no separate .dat files any longer. There are 'z.VA: feature name' and 'z.ST: feature name' configuration maps that drive the Feature Load/Unload function. You will notice also 'zz.whatever' maps that are used internally.

There is no documentation available on how to construct these maps, but it should be reasonably obvious. The only tricky bit is that you need to create a comment for the map in the proper form -- you should be able to figure this out by looking at one of the existing z. maps.

[marten]

The only tricky bit is that you need to create a comment for the map in the proper form -- you should be able to figure this out by looking at one of the existing z. maps.

Found it ...

Marten