From: Thomas Zimmermann <tzimmermann@suse.de> To: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Cc: "Jani Nikula" <jani.nikula@linux.intel.com>, "Javier Martinez Canillas" <javierm@redhat.com>, linux-fbdev@vger.kernel.org, "David Airlie" <airlied@linux.ie>, "Daniel Vetter" <daniel.vetter@ffwll.ch>, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, "Noralf Trønnes" <noralf@tronnes.org>, "Geert Uytterhoeven" <geert@linux-m68k.org>, "Maxime Ripard" <maxime@cerno.tech>, "Sam Ravnborg" <sam@ravnborg.org> Subject: Re: [PATCH v4 1/6] drm/format-helper: Add drm_fb_xrgb8888_to_gray8_line() Date: Mon, 14 Feb 2022 13:12:48 +0100 [thread overview] Message-ID: <5ee24960-7843-827a-2c47-b93a4b4798e3@suse.de> (raw) In-Reply-To: <YgoxFBGNsrezVxmi@smile.fi.intel.com> [-- Attachment #1.1: Type: text/plain, Size: 2115 bytes --] Hi Am 14.02.22 um 11:38 schrieb Andy Shevchenko: > On Mon, Feb 14, 2022 at 10:03:53AM +0100, Thomas Zimmermann wrote: >> Am 11.02.22 um 16:41 schrieb Andy Shevchenko: > > ... > >>>> IMO *always* prefer a for loop over while or do-while. >>>> >>>> The for (i = 0; i < N; i++) is such a strong paradigm in C. You >>>> instantly know how many times you're going to loop, at a glance. Not so >>>> with with the alternatives, which should be used sparingly. >>> >>> while () {} _is_ a paradigm, for-loop is syntax sugar on top of it. >> >> Naw, that's not true. > > In the section 3.5 "Loops - While and For" in "The C Programming > Language" 2nd by K&R, the authors said: Year of publication: 1988 . It's not the most up-to-date reference for C programming. > > The for statement ... is equivalent to ... while..." > > They said that for is equivalent to while, and not otherwise. Even leaving readability aside, it's not equivalent. You can declare variables as part of the for statement. (I know it's not the kernel's style.) Also, 'continue' statements are not well-suited in for loops, because it's non-obvious if the loop's update statement is being executed. (It isn't.) > > Also, syntax sugar by definition declares something that can be written as > a single line of code, which usually is done using more (not always). The discussion has entered the phase of hair splitting. Good. Best regards Thomas > >> An idiomatic for loop, such as for (i = ...; i < N; >> ++i), is such a strong pattern that it's way better than the corresponding >> while loop. > >>>> And yes, the do-while suggested above is buggy, and you actually need to >>>> stop and think to see why. >>> >>> It depends if pixels can be 0 or not and if it's not, then does it contain last >>> or number. >>> >>> The do {} while (--pixels); might be buggy iff pixels may be 0. > -- Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 840 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Zimmermann <tzimmermann@suse.de> To: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Cc: linux-fbdev@vger.kernel.org, "David Airlie" <airlied@linux.ie>, "Daniel Vetter" <daniel.vetter@ffwll.ch>, "Javier Martinez Canillas" <javierm@redhat.com>, linux-kernel@vger.kernel.org, "Noralf Trønnes" <noralf@tronnes.org>, "Geert Uytterhoeven" <geert@linux-m68k.org>, dri-devel@lists.freedesktop.org, "Sam Ravnborg" <sam@ravnborg.org>, "Maxime Ripard" <maxime@cerno.tech> Subject: Re: [PATCH v4 1/6] drm/format-helper: Add drm_fb_xrgb8888_to_gray8_line() Date: Mon, 14 Feb 2022 13:12:48 +0100 [thread overview] Message-ID: <5ee24960-7843-827a-2c47-b93a4b4798e3@suse.de> (raw) In-Reply-To: <YgoxFBGNsrezVxmi@smile.fi.intel.com> [-- Attachment #1.1: Type: text/plain, Size: 2115 bytes --] Hi Am 14.02.22 um 11:38 schrieb Andy Shevchenko: > On Mon, Feb 14, 2022 at 10:03:53AM +0100, Thomas Zimmermann wrote: >> Am 11.02.22 um 16:41 schrieb Andy Shevchenko: > > ... > >>>> IMO *always* prefer a for loop over while or do-while. >>>> >>>> The for (i = 0; i < N; i++) is such a strong paradigm in C. You >>>> instantly know how many times you're going to loop, at a glance. Not so >>>> with with the alternatives, which should be used sparingly. >>> >>> while () {} _is_ a paradigm, for-loop is syntax sugar on top of it. >> >> Naw, that's not true. > > In the section 3.5 "Loops - While and For" in "The C Programming > Language" 2nd by K&R, the authors said: Year of publication: 1988 . It's not the most up-to-date reference for C programming. > > The for statement ... is equivalent to ... while..." > > They said that for is equivalent to while, and not otherwise. Even leaving readability aside, it's not equivalent. You can declare variables as part of the for statement. (I know it's not the kernel's style.) Also, 'continue' statements are not well-suited in for loops, because it's non-obvious if the loop's update statement is being executed. (It isn't.) > > Also, syntax sugar by definition declares something that can be written as > a single line of code, which usually is done using more (not always). The discussion has entered the phase of hair splitting. Good. Best regards Thomas > >> An idiomatic for loop, such as for (i = ...; i < N; >> ++i), is such a strong pattern that it's way better than the corresponding >> while loop. > >>>> And yes, the do-while suggested above is buggy, and you actually need to >>>> stop and think to see why. >>> >>> It depends if pixels can be 0 or not and if it's not, then does it contain last >>> or number. >>> >>> The do {} while (--pixels); might be buggy iff pixels may be 0. > -- Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-02-14 12:12 UTC|newest] Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-11 9:19 [PATCH v4 0/6] drm: Add driver for Solomon SSD130x OLED displays Javier Martinez Canillas 2022-02-11 9:19 ` Javier Martinez Canillas 2022-02-11 9:19 ` [PATCH v4 1/6] drm/format-helper: Add drm_fb_xrgb8888_to_gray8_line() Javier Martinez Canillas 2022-02-11 9:19 ` Javier Martinez Canillas 2022-02-11 9:29 ` Thomas Zimmermann 2022-02-11 10:28 ` Andy Shevchenko 2022-02-11 10:28 ` Andy Shevchenko 2022-02-11 10:40 ` Javier Martinez Canillas 2022-02-11 10:40 ` Javier Martinez Canillas 2022-02-11 11:12 ` Andy Shevchenko 2022-02-11 11:12 ` Andy Shevchenko 2022-02-11 11:54 ` Thomas Zimmermann 2022-02-11 11:54 ` Thomas Zimmermann 2022-02-11 12:05 ` Jani Nikula 2022-02-11 12:11 ` Javier Martinez Canillas 2022-02-11 12:27 ` Geert Uytterhoeven 2022-02-11 12:27 ` Geert Uytterhoeven 2022-02-11 15:41 ` Andy Shevchenko 2022-02-11 15:41 ` Andy Shevchenko 2022-02-11 16:25 ` Jani Nikula 2022-02-11 16:25 ` Jani Nikula 2022-02-11 17:27 ` Andy Shevchenko 2022-02-11 17:27 ` Andy Shevchenko 2022-02-14 9:17 ` Pekka Paalanen 2022-02-14 9:17 ` Pekka Paalanen 2022-02-14 10:26 ` Andy Shevchenko 2022-02-14 10:26 ` Andy Shevchenko 2022-02-14 9:03 ` Thomas Zimmermann 2022-02-14 9:03 ` Thomas Zimmermann 2022-02-14 10:38 ` Andy Shevchenko 2022-02-14 10:38 ` Andy Shevchenko 2022-02-14 10:52 ` Simon Ser 2022-02-14 10:52 ` Simon Ser 2022-02-14 10:57 ` Geert Uytterhoeven 2022-02-14 10:57 ` Geert Uytterhoeven 2022-02-14 12:12 ` Thomas Zimmermann [this message] 2022-02-14 12:12 ` Thomas Zimmermann 2022-02-14 12:47 ` Ville Syrjälä 2022-02-14 12:47 ` Ville Syrjälä 2022-02-14 12:54 ` Thomas Zimmermann 2022-02-14 13:07 ` Ville Syrjälä 2022-02-14 13:59 ` Andy Shevchenko 2022-02-14 13:59 ` Andy Shevchenko 2022-02-11 9:19 ` [PATCH v4 2/6] drm/format-helper: Add drm_fb_xrgb8888_to_mono_reversed() Javier Martinez Canillas 2022-02-11 9:19 ` Javier Martinez Canillas 2022-02-11 11:10 ` Andy Shevchenko 2022-02-11 11:10 ` Andy Shevchenko 2022-02-11 11:50 ` Javier Martinez Canillas 2022-02-11 11:50 ` Javier Martinez Canillas 2022-02-11 15:55 ` Andy Shevchenko 2022-02-11 15:55 ` Andy Shevchenko 2022-02-11 11:59 ` Thomas Zimmermann 2022-02-11 11:59 ` Thomas Zimmermann 2022-02-11 12:46 ` Thomas Zimmermann 2022-02-11 12:46 ` Thomas Zimmermann 2022-02-11 9:19 ` [PATCH v4 3/6] drm: Add driver for Solomon SSD130x OLED displays Javier Martinez Canillas 2022-02-11 9:19 ` Javier Martinez Canillas 2022-02-11 11:33 ` Andy Shevchenko 2022-02-11 11:33 ` Andy Shevchenko 2022-02-11 12:05 ` Javier Martinez Canillas 2022-02-11 12:05 ` Javier Martinez Canillas 2022-02-11 12:23 ` Geert Uytterhoeven 2022-02-11 12:23 ` Geert Uytterhoeven 2022-02-11 12:27 ` Javier Martinez Canillas 2022-02-11 12:27 ` Javier Martinez Canillas 2022-02-11 15:49 ` Andy Shevchenko 2022-02-11 15:49 ` Andy Shevchenko 2022-02-11 12:44 ` Thomas Zimmermann 2022-02-11 12:44 ` Thomas Zimmermann 2022-02-11 9:19 ` [PATCH v4 4/6] drm/solomon: Add SSD130x OLED displays I2C support Javier Martinez Canillas 2022-02-11 9:19 ` Javier Martinez Canillas 2022-02-11 11:16 ` Andy Shevchenko 2022-02-11 11:16 ` Andy Shevchenko 2022-02-11 9:21 ` [PATCH v4 5/6] MAINTAINERS: Add entry for Solomon SSD130x OLED displays DRM driver Javier Martinez Canillas 2022-02-11 9:21 ` Javier Martinez Canillas 2022-02-11 11:34 ` Andy Shevchenko 2022-02-11 11:34 ` Andy Shevchenko 2022-02-11 9:22 ` [PATCH v4 6/6] dt-bindings: display: ssd1307fb: Add myself as binding co-maintainer Javier Martinez Canillas 2022-02-11 9:22 ` Javier Martinez Canillas 2022-02-11 11:35 ` Andy Shevchenko 2022-02-11 11:35 ` Andy Shevchenko
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=5ee24960-7843-827a-2c47-b93a4b4798e3@suse.de \ --to=tzimmermann@suse.de \ --cc=airlied@linux.ie \ --cc=andriy.shevchenko@linux.intel.com \ --cc=daniel.vetter@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=geert@linux-m68k.org \ --cc=jani.nikula@linux.intel.com \ --cc=javierm@redhat.com \ --cc=linux-fbdev@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=maxime@cerno.tech \ --cc=noralf@tronnes.org \ --cc=sam@ravnborg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.