Bill Pringlemeir wrote: > I think they are two different uses/meanings. I see this but to me it's rather subtle. I changed it because I thought it was wrong or at least read somewhat awkward. If CVS would work ATM, I or someone else would gratefully apply your suggestions.
> I also think that Goggle has bad grammar! Sure, but it's not as bad as some people claim. If one looks closely at the sentences which are found, you're usually on the right side. The ratio alone can be wrong, of course, if a combination of words may be used in completely different ways. YMMV. > My concern is that people, > using LimeWire, BearShare, etc., might see GTKG sending this message > and get the wrong impression about the code. Judge not code by the grammar, that ye be not judged by your code. ;-) I mean how many native English speaker handle *any* other language reasonably well? Of course, it always looks a little incompetent when people don't use a language perfectly. Highly intelligent people may appear as fools even. However, GTKG is much more verbose than most other vendors' servents and, AFAIK, most users won't even see our precious error messages. > btw. That was my only nit in the many recent changes. Although I > glossed over the GTK2 changes, because I don't know a lot about GTK > (or at least less than 'C'). In my experience, you really have to *use* GTK+ to understand it and find appropriate usage schemes. The documentation itself doesn't mention a lot of subtle things and you often have to peek at the source code to decide what's better or worse. There are mainly two things that suck especially in GLib/GTK+ 2.x. First, the excessive use of dynamically allocated memory. In theory that's cleaner but it causes severe performance penalties due to memory copies (cache killer) and can easily cause memory leaks. The other bad thing is the internal use of UTF-8. That's OK for accessing files but internal and for the GUI you want to use a flat encoding. -- Christian
pgpqYDafmMD58.pgp
Description: PGP signature
