>Hi Fernando,
>
>thanks for replieing.
>
>Sounds good.
>
>I've thought a bit around it and found two ideas
>
>#1 split and cat athe text file.
>
>#2 split and cat the vcx
>
>I think #2 easier. because it would just create vcx's like
>YourClassLib.YourClass.vcx
>
>This could be more or less achieved by scanning the vcx and creating a new table out of header record and the class contents
>The rest is your default class to prg - just for more libs
>
>The opposite way build the little vcxs oput of the little prgs and then gather them to one new large one.
>Should be simple. :)
>
>
>In the end it should produce something like
>
>YourClassLib.YourClass.pr2
>
>I find it much more comfortable to merge single classes than large Lbs. :)
>
>So for git I would just include *.*.pr2 classes and that's it.
>
>


Yes, it's something like this (#1), like TwoFox did with classes. But those who will use this class-per-file should control all the separated files (will be a hell of files!, trust me), and forgetting one file could mean an invalid binary, but this risk will be avaluated for anybody.

I preffer the single file, because developers can visually check "2 binaries + 1 tx2", but when you have "N" tx2 files, you have no visual control anymore, because you don't know how many files to expect, so it's prone to many errors.

I've used TwoFox up to last year, and I really don't like so many files created. In a system with 2700 files, on which 100 are classlibraries, you could get, easy, more than 3000+ files, a quantity too difficult to manipulate.

But, hey!, let's see what happens and let people decide and share their experiennces with this new option! Who knows? :D


About #2 (split vcx), this definetely will not be good, because the vcx must be compiled, and it must be a valid vcx. Having more vcx is a question of design, not a conversion one.


Best Regards!