Re: GObject's property with _ issue
Piotras <pp-VVDi8QVAvoBWk0Htik3J/[email protected]> Mon, 20 Feb 2006 11:36:10 +0100
| Newsgroups | gmane.comp.web.midgard.devel |
|---|---|
| Message-ID | <[email protected]> |
"Jukka Zitting" <[email protected]> wrote: > Hi, Hi, > > 1. Trigger an error while schema is parsed? > > 2. Trigger a warning and wait for unconditional errors? > > 3. Use black magic for such properties? > > > > The first one seems to me the only one solution. > > With 1 we should define CamelCase as the preferred property naming > convention. This is a bit awkward as it interferes with the GObject > naming convention. This is some solution but think about PHP (again) :/ Its love to use only lowercases everywhere makes me very frustrated sometimes. > Option 3 is also reasonable, we'd need to translate dashes back to > underscores in language bindings and when generating SQL. That's why I wrote 'black magic'. If the property has dash defined then we will brake it. Piotras