Questions

(One intermediate revision by the same user not shown)

Line 18:

*Q: Why doesn't <tt>du</tt> take an -i argument for inode usage?

*A: It's difficult (and impossible for regular users) to map directory hierarchies to inodes.

*A1: It's difficult (and impossible for regular users) to map directory hierarchies to inodes.

*A2: Newer versions of <tt>util-linux</tt> <i>do</i> support <tt>--inodes</tt> as an argument to <tt>du</tt>!

===Linux===

*Q: How can I discover a module's parameters?

Line 41:

Line 42:

==[[C]]==

*Q: Why aren't ''"target"''-style <tt>#includes</tt> a good idea with any sane compiler?

*A: So long as you can append to the default include search path (ie, the <tt>-I</tt> option to [[gcc]]), the ''<target>''-style include can search in your project directory. Building from the source toplevel, a simple <tt>-I.</tt> added to CFLAGS allows #include ~~<~~toplevel/relative/filename~~>~~. Moved headers will trigger a preprocessing failure. If ''"target"''-style <tt>#includes</tt> are used, the directory of the source being compiled is typically searched prior to other include paths. This means moving source files or introducing new headers can change the files being included, which is almost always undesirable.

*A: So long as you can append to the default include search path (ie, the <tt>-I</tt> option to [[gcc]]), the ''<target>''-style include can search in your project directory. Building from the source toplevel, a simple <tt>-I.</tt> added to CFLAGS allows <tt>#include <toplevel/relative/filename></tt>. Moved headers will trigger a preprocessing failure. If ''"target"''-style <tt>#includes</tt> are used, the directory of the source being compiled is typically searched prior to other include paths. This means moving source files or introducing new headers can change the files being included, which is almost always undesirable.

===[[GCC]]===

*Q: How do I see which optimization flags are enabled with -Ox?

Questions: Difference between revisions

Dank (talk | contribs)

@@ Line 18: / Line 18: @@
 *Q: Why doesn't <tt>du</tt> take an -i argument for inode usage?
-*A: It's difficult (and impossible for regular users) to map directory hierarchies to inodes.
+*A1: It's difficult (and impossible for regular users) to map directory hierarchies to inodes.
+*A2: Newer versions of <tt>util-linux</tt> <i>do</i> support <tt>--inodes</tt> as an argument to <tt>du</tt>!
 ===Linux===
 *Q: How can I discover a module's parameters?
@@ Line 41: / Line 42: @@
 ==[[C]]==
 *Q: Why aren't ''"target"''-style <tt>#includes</tt> a good idea with any sane compiler?
-*A: So long as you can append to the default include search path (ie, the <tt>-I</tt> option to [[gcc]]), the ''&lt;target&gt;''-style include can search in your project directory. Building from the source toplevel, a simple <tt>-I.</tt> added to CFLAGS allows #include &lt;toplevel/relative/filename&gt;. Moved headers will trigger a preprocessing failure. If ''"target"''-style <tt>#includes</tt> are used, the directory of the source being compiled is typically searched prior to other include paths. This means moving source files or introducing new headers can change the files being included, which is almost always undesirable.
+*A: So long as you can append to the default include search path (ie, the <tt>-I</tt> option to [[gcc]]), the ''&lt;target&gt;''-style include can search in your project directory. Building from the source toplevel, a simple <tt>-I.</tt> added to CFLAGS allows <tt>#include <toplevel/relative/filename></tt>. Moved headers will trigger a preprocessing failure. If ''"target"''-style <tt>#includes</tt> are used, the directory of the source being compiled is typically searched prior to other include paths. This means moving source files or introducing new headers can change the files being included, which is almost always undesirable.
 ===[[GCC]]===
 *Q: How do I see which optimization flags are enabled with -Ox?