Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate concept of "namespace" and file name #31

Open
JCash opened this issue Sep 5, 2020 · 3 comments
Open

Separate concept of "namespace" and file name #31

JCash opened this issue Sep 5, 2020 · 3 comments

Comments

@JCash
Copy link
Contributor

JCash commented Sep 5, 2020

Currently multiple documents cannot share the same "@namespace".
If they do, only one of these "@document" tags' info will be added.
And, since a document has a separate include file path, this gets wrong quickly.

E.g. hash.h and dstrings.h both reside in the global namespace, but you need two different includes to use these functions.

@britzl
Copy link
Collaborator

britzl commented Sep 6, 2020

I'm not sure I understand the problem. Can you please elaborate?

@JCash
Copy link
Contributor Author

JCash commented Sep 6, 2020

For instance, there is no namespace called "dmStringFunc", yet, we call it that, and the file link is named "dmStringFunc".
In practice, those string functions are part of the global namespace "::"
However, we don't want to gather all functions in the global namespace under one page, since they have different contexts, different functionality and different documentation, and also the link to the header files are different.
Here is a list of functions/structs/macros in the global namespace: DM_ALIGN, dmArray, dmHash*, dmStr*, dmLog*

@JCash
Copy link
Contributor Author

JCash commented Sep 6, 2020

In short, I cannot set "namespace" to an empty value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants