Re: Pango Performance (was: Re: --gtk-unbuffered)
- From: Federico Mena Quintero <federico ximian com>
- To: jrb redhat com
- Cc: gtk-devel-list gnome org
- Subject: Re: Pango Performance (was: Re: --gtk-unbuffered)
- Date: Thu, 1 Mar 2001 17:59:13 -0600
jrb redhat com writes:
> egger suse de writes:
>
> > On 1 Mar, Tor Lillqvist wrote:
> >
> > > > + return (1 == has_glyph);
> >
> > > It would be preferrable if all of Pango used the same coding style
> > > conventions. While I certainly understand the rationale for this style
> > > of writing equality tests, it is nonetheless not used in any of the
> > > other code, which can be confusing. Or what do others think?
> >
> > Just curious: Whats the rationale for this "strange way to code"?
>
> It catches the '=' vs '==' errors. For instance:
>
> return (has_glyph = 1);
> return (has_glyph == 1);
>
> are both valid.
>
> return (1 = has_glyph);
>
> is not.
This is *fantastically* ugly.
Federico
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]