Re: Why both macro definitions and struct declarations are included in sched.c?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



" It's especially important to put a declaration or definition in a
header file when it will be shared between several other files"

I guess those definitions or declarations are used only in sched.c ,
so there is no reason to put them in header file.

Daniel.

On Wed, Aug 6, 2008 at 5:05 PM, ZelluX <zellux@xxxxxxxxx> wrote:
> Hi all
>
> I'm learning scheduling algorithm and reading sched.c
> (http://lxr.linux.no/linux+v2.6.11/kernel/sched.c) , and come up with a
> question.
>
> As C FAQ 10.6 points out, macro definitions and struct declarations should
> be put in header files(http://c-faq.com/cpp/hfiles.html)
>
> But sched.c violates this convention and put all the definitions and
> declarations in a single .c file, so is there any advantage of doing this
> instead of creating another sched.h?
>
> Many thanks for your reply.
>

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux