Re: dual line backtraces for i386.

On 1/6/06, Jan Engelhardt <[email protected]> wrote:
> >> >                         printk(space == 0 ? "     " : "\n");
> >> >                         space = !space;
> >>
> >> readability ?
> >
> >Well, if I were going for _un_readability I'd have suggested:
> >
> >        printk(space = !space ? "     " : "\n");
>
> Anyone voting for "\t" instead of "     "?

Sure: if you use '\t' then you can do:

printk("%c", 9+space++);
space &= 1;

No branches ;)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: dual line backtraces for i386.
    • From: Mitchell Blank Jr <[email protected]>

• References:
  • Re: dual line backtraces for i386.
    • From: Chuck Ebbert <[email protected]>
  • Re: dual line backtraces for i386.
    • From: Jan Engelhardt <[email protected]>

• Prev by Date: Re: [2.6 patch] remove drivers/net/tulip/xircom_tulip_cb.c
• Next by Date: Re: command line parsing broken in 2.6.15-git?
• Previous by thread: Re: dual line backtraces for i386.
• Next by thread: Re: dual line backtraces for i386.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]