-
-
Notifications
You must be signed in to change notification settings - Fork 279
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
Add vendor prefixes: rGuiName #5
Comments
Hi @inlife! Glad you like this little project! :) Personally I don't like vendor prefixes, I avoided it on raylib and also would like to avoid it on raygui... but I'm concerned about the possible name collisions with other libraries (already dealt with that trying to include the infamous In any case, I need to think about that... already considered using a EDIT: By the way, I'm following your librg library, considering it as a candidate library to add network functionality to raylib. |
Well yea, however I think, when you are using something like raylib, you are using it not as a library but more like as a framework. Something bigger, something that defines global rules for your application, where you, as developer, is supposed just to follow them. However that still won't save you from having name collisions with something having those simple method names. Easiest way would be to use namespaces, however as we know, C doesnt have those badboys :D
That is something what is definitely worth thinking about. And thinking quite a lot, I'd say. This is a major design decision, which in theory can be applied not only to the raygui, but for raylib and even raylib lua. It's something that not just changes name methods, however makes a paradigm shift in your brain I suppose. Anyway, for now I just suggest think about it, at least for a few weeks/months. That should give you, and others, answer "is this really worth it".
Oh that is so nice to hear. Thank you! I would also suggest looking into more low-level ENet library, we are using at as a backend in the librg. |
No plans to add vendor prefixes for the upcoming v2.0. Just closing this issue for now. |
Hello,
First of all, very nice project, and what is the most important (for me), is a beautiful gfx style. :D
However, I have a suggestion. Would it be hard to add a vendor prefix to each public method of the library? That could prevent some name collisions which are theoretically possible right now. Especially for occasions where whole user's project codebase uses "unity builds" approach.
That is a major breaking change in API though. So what do you think about it?
Thank you!
The text was updated successfully, but these errors were encountered: