Hey Y'all,
@Martin_fr:
Thanks for that!!
I'm aware of the use of dotted namespacing ever since it was introduced in 3.0.
I've been using it ever since. I was overjoyed when I saw that this carried over from Delphi.
@marcov:
Is there a a link that gives more info on the -FN to set scope prefixes?
If this is what I think, it would,
probably, solve my issue.
Well, it's not an issue, it's more of a curiosity, but hey, that's how we learn right?
@ccrause:
Assuming you are using Lazarus to manage the project: Create separate build profiles for the two libraries in your test project, where each library's build mode sets the Other unit files setting to point to that library's source folder, and separate Unit output directories so that the compiled units don't clash.
This option is what I'm trying to avoid. I'm also trying to avoid having 3 diff projects, one for each lib.
I've been aware of dotted namespacing since FPC 3.0 and I've been using it extensively in my personal projects.
My goal here is to have a comparison of all 3 libraries in one single executable, if at all possible.
I'm not quite sure this goal is attainable, since
fpc-mardown is a fork of
delphi-markdown and they use the same(non dotted namespaced) unit names.
Hence me asking if having them in different packages would allow me to prefix the unit name with the package name.
I'm lost and in need of the forum's overwhelming knowledge of the more savvy users!!
Cheers,
Gus