1. the original code from Otto put each method in a file
2. I liked the idea of using git to manage method versions - and it is a
really cool
feature as git is able to maintain the history of a method (file)
as the method is
moved from class to class
3. Using directory structure actually enhanced the ability to create a
cross-platform
scheme, since directory structure parsing is easier than coming to
an agreement
on a common "fileout" format
With that said, assuming that a common fileout format can be agreed upon
...
there's no reason that a file per package or file per class format could be
invented ... If you or anyone else has the time to create such a beast
then I say go for it ...
Given that we have a functional disk representation in hand, I don't
think that searching for a new format (that will have it's own flaws) is
a top priority ... regardless of what the disk format looks like there
is a real void when it comes to the tool set ....
Finally the smalltalk community is not the only group that has trouble
using git on windows because of the file path limitation ... so these
guys that do file per package still run into trouble when using git on
windows:)
Dale
On 9/30/15 11:57 AM, Alexandre Bergel wrote:
Why not having just one folder level? As we would have in any other
language? One folder per package, and inside a .st file per class.
Alexandre
Le 30 sept. 2015 à 18:47, Dale Henrichs
<[email protected]
<mailto:[email protected]>> a écrit :
