Date: 2004-04-28T07:38:34
Editor: 138.189.119.133 <>
Wiki: Jakarta HiveMind Wiki
Page: PrivatesProposal
URL: http://wiki.apache.org/jakarta-hivemind/PrivatesProposal
no comment
Change Log:
------------------------------------------------------------------------------
@@ -13,3 +13,7 @@
= Discussion =
At the risk of violating ["YAGNI"], perhaps better scoping rules are needed.
That is, something reminiscent of Java's protected modified, where a extension
point would be visible within sub-modules. But what defines a sub-module? A
module which has the current (exporting) module's id as a prefix?
+
+KnutWannheden: The solution (it's really a workaround) to the corresponding
problem in Ant (private targets) is to prefix the target name with a dash (e.g.
{{{<target name="-internal"/>}}}). The target can't be invoked because the Ant
command line frontend would parse it as an option (which doesn't exist). I
suppose a pragmatic solution like this wouldn't work in HiveMind nor would it
be desirable...
+
+To minimize the knowledge needed by the user maybe a best practice would often
suffice. The private and public parts could be split into two modules, as
common in Java with ''.internal'' and ''.impl'' packages.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
