Mirror of forum.nim-lang.org

4370 :: Do we really like or need single letter prefixes like w, m... in public libs?

• Stefan_Salewski (orginal) [2018-11-09T16:16:47+01:00] view original

  Just saw in recent tread: (https://forum.nim-lang.org/t/4366)

  
  wNim
  wFrame
  mWhichButton
  wOkCancel
  wIdOk
  Run

  and some more.

  I guess w may refer to windows or to module author name, for the m I have no idea at all. Maybe it is because Araq likes to use such prefixes for his inpure enums in compiler code. There that may be OK (and generally is at least two letters) but I can't say I like such single letter prefixes for libs like GUI lib that match. (For gintro I avoided prefixes generally, with some rare exceptions like GObject or GMessage. I had no really trouble with name conflicts, and in case of conflict I personally prefer gtk.button over gbutton.)

---

• juancarlospaco (orginal) [2018-11-09T20:58:40+01:00] view original

  https://nim-lang.org/docs/apis.html

---

• mashingan (orginal) [2018-11-10T06:29:25+01:00] view original

  I think it's to balance out between Win32 naming and Nim proc naming. So the proc is still starting with lowercase and still retain the original Win32 API naming. Maybe.

---

• Ward (orginal) [2018-11-10T06:43:12+01:00] view original

  Here "w" prefix means the wNim library is for Windows only and inspired by wxWidgets. And "m" prefix means member variables. These variables are used by library internally and should not be public to the user.

---

• Araq (orginal) [2018-11-10T10:17:24+01:00] view original

  Nim calls these "fields", not "members", btw.

---

• dom96 (orginal) [2018-11-11T16:23:15+01:00] view original

  No. I really don't like that. The thread you link to doesn't follow conventions in multiple places, primarily with regards to upper case type names.

---