Susu
Community Contributors
- Messages
- 13
- Points
- 0
- Github
- Earisu
Hi,
As some of you may have noticed, I helped a little with the renewal phase one and HPM system, converting some files into interface (based on what you gys already started).
I was converting the map.c with my tools (HerculesInterfaceMaker) and noticed when that was done there was a conflict with the interface name "map" because there was already a var with that name (map_data *map) and it created a conflict.
I already got the same problem with the db.c file, and I just named the interface DB (caps).
So I was thinking it could be nice to have a naming convention for all the current and future interface, this would be easier for developpers and more user-friendly.
What do you think ?
As some of you may have noticed, I helped a little with the renewal phase one and HPM system, converting some files into interface (based on what you gys already started).
I was converting the map.c with my tools (HerculesInterfaceMaker) and noticed when that was done there was a conflict with the interface name "map" because there was already a var with that name (map_data *map) and it created a conflict.
I already got the same problem with the db.c file, and I just named the interface DB (caps).
So I was thinking it could be nice to have a naming convention for all the current and future interface, this would be easier for developpers and more user-friendly.
What do you think ?