Stas Bekman wrote: > > My last suggestion was to have a single file with test and config > inside. The problem is scanning many files, which I suggested to solve > by having a special naming (e.g. .ct instead of .t) to mark certain > files that they include extra configuration.
I would prefer to have the one-time-per-setup overhead of scanning all the .t files, rather than polluting the namespace with special-purpose extension. MHO. -- #ken P-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ "All right everyone! Step away from the glowing hamburger!"
