Thanks much, Alex.
But how do you physically partition the namespace within a module, if not by
sub-folders?
I am not sure whether the following example is, by definition, of a submodule
that one could import by writing "import Cacao.StyleKit":
Https://github.com/PureSwift/Cacao/tree/master/Sources/Cacao/StyleKit
Sent from ProtonMail mobile
-------- Original Message --------
On 13.09.2017, 10:23, Alex Blewitt wrote:
> No, submodules in Swift bear little relation to sub packages in Java. It's
> really just a way of partitioning the namespace within a single module. Nor
> is there any relation between the path and the name of the module either.
>
> Alex
>
>> On 12 Sep 2017, at 22:41, blaster_in_black via swift-users <
>> swift-users@swift.org> wrote:
>>
>> Hi,
>>
>> I am beginning with Swift 4 (coming from the Java world) but I do not have
>> yet a Swift development environment to experiment with. Therefore my
>> question(s) might sound a bit silly. Unfortunately, I haven't been able to
>> answer them by reading the online Language Guide.
>>
>> 1) What makes a submodule? I can see online examples about how to import
>> them, but not how to create one or any other further details about them. Are
>> they like Java packages inside a jar? Do their hierarchical name (
>> prefix1.prefix2. ... .submodulename) reflect a path tree on the filesystem
>> (/ prefix1/prefix2. ... /submodulename), just as it happens with Java
>> packages?
>> 2) Can two different submodules within a single module export two different
>> classes under a single class name? Like module.submodule1.MyType and
>> module.submodule2.myType.
>>
>> Thanks in advance.
>>
>> David
>>
>> _______________________________________________
>> swift-users mailing list
>> swift-users@swift.org
>> https://lists.swift.org/mailman/listinfo/swift-users
_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users