I think one important aspect of Java's java.foo.bar style has been
overlooked: the semantics. sure, syntactivally, java.foo.bar and
java_foo_bar; they're basically the same. the big issue (to me, at
least) is that the Java compiler knows how to interpret the .s and
will use them to navigate
On Wed, 10 Oct 2001, Hal Daume III wrote:
(snip)
least) is that the Java compiler knows how to interpret the .s and
will use them to navigate directory structure.
(snip)
Yes, that's certainly an interesting idea. I'd like to fall short of
mandating anything about location of source files in
So, barring this, I'm curious how other people handle this issue.
I have multiple projects. Call them A, B, C. They are in directories:
~/projects/A
~/projects/B
~/projects/C
repsectively.
Say I'm creating a new project, D, in ~/projects/D that uses code that
I've written in packages A,
On Wed, Oct 10, 2001 at 03:29:03PM -0400, Hal Daume III wrote:
So, barring this, I'm curious how other people handle this issue.
I have multiple projects. Call them A, B, C. They are in directories:
~/projects/A
~/projects/B
~/projects/C
repsectively.
Say I'm creating a new