rtems/src/scheduler* code convention issue

[Gedare Bloom]

Is there a written rule for what constitutes "deep" nesting? I find 3
levels not that deep, albeit if unnecessary.

Perhaps the author preferred to have a single exit point?

-Gedare

On Mon, May 12, 2014 at 7:28 PM, Joel Sherrill
<joel.sherrill at oarcorp.com> wrote:
> Hi
>
> Both schedulerident.c and schedulergetprocessorset.c do not follow
> RTEMS Coding Conventions on avoidance of deep nesting by using
> early returns. The nesting on schedulergetprocessorset.c is pretty
> ugly and could have been avoided easily.
>
> --
> Joel Sherrill, Ph.D.             Director of Research & Development
> joel.sherrill at OARcorp.com        On-Line Applications Research
> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
> Support Available                (256) 722-9985
>
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-devel