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

name of type #11

Closed
Alexey-T opened this issue Sep 22, 2017 · 5 comments
Closed

name of type #11

Alexey-T opened this issue Sep 22, 2017 · 5 comments

Comments

@Alexey-T
Copy link

Alexey-T commented Sep 22, 2017

XMLString = DOMString;
maybe in big app, app uses anotjher XML lib, and XMLString name is busy. maybe use name XavString?

@Alexey-T
Copy link
Author

Alexey-T commented Sep 22, 2017

and other names too: maybe use IXavNNNNNN ?

@mdbs99
Copy link
Owner

mdbs99 commented Sep 22, 2017

In this case, XMLString it is not (only) a prefix, but a context.

Some years ago, I used such prefixes to prevent collision names. Then, I realized that is this is a false precaution. For example, I already used "MD" — as you use "AT" — but I found some other lib that used the same. We cannot control the entire world, ie, what millions of programmers will choose to use as prefix for their libs, right?

IMO, it's better to use "borderline units", which means that you will use some lib in certain units but not in all unit of your project. I wrote about it here.

The real prefix is the unit.

@mdbs99
Copy link
Owner

mdbs99 commented Sep 22, 2017

@nunopicado what do you think?

@nunopicado
Copy link
Contributor

I used to think the same way, using preffixes. But the problem is what you said, we can not control the world.
Careful usage of units and FQINs might be a safer path.

@mdbs99
Copy link
Owner

mdbs99 commented Sep 28, 2017

No one talking so, I'm closing this issue.

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

3 participants