I’m pretty sure the above snippet is equivalent to this:
using ..TimeFrames
using ..Prices
using ..CoreDates
Or you could do it in a single line, like using ..TimeFrames, ..Prices, ..CoreDates.
Note that, in my code, I prefer import to using, and I like to use fully qualified names; this is, however, just my stylistic preference. In fact, most Julia programmers seem to largely shy away from (sub)modules in their code.
My goal was to get it working. Then I could find what liberty I have in working code.
You are correct …Module worked as well. I just seemed to have missed it in my reading. @Benny and maybe others mentioned it.
If not submodules then everything is an independent package?
Some of my submodules have no meaning outside of the package and it is simply helps keep a large code base clean. At least this one. But as I refactor the code to be more Julia idiomatic I will see what happens.
PkgTemplates gives an older manifest file, but you can get rid of the warning easily:
julia> using Pkg
julia> Pkg.upgrade_manifest()
It also looks like you are in your Julia folder, but you should be in the root folder of your package. When you activate, you can just do activate .
Also, does your package contain a file src/RhythemTrader.jl ? This is the root of the package and should be created by PkgTemplates. This is the highest level module (called RhythemTrader), in which you should have all the includes for the other files.