<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Maybe we need a new directory for "exported" header files.<br>
<br>
$MODULE/exported<br>
<br>
That way, it lives inside the module, but it's obvious that it's
part of the external facing API.<br>
<br>
On 2012-02-21 16:34, Eike Rathke wrote:
<blockquote cite="mid:20120221143419.GB2522@isigqoko.erack.de"
type="cite">
<pre wrap="">Hi Tor,
On Tuesday, 2012-02-21 10:02:50 +0200, Tor Lillqvist wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Has the time come to get rid of the "delivering" step for public
headers? I.e. for a header <MODULE/BAR.hxx>, instead of having it in
MODULE/inc/MODULE/BAR.hxx and then copying it to
solver/INPATH/inc/MODULE/BAR.hxx as part of the "make" of MODULE, it
could be directly in a new top-level "inc" directory, in
inc/MODULE/BAR.hxx all the time. (Obviously -I$(SRC_ROOT)/inc would
have to be added to the compilation flags.)
</pre>
</blockquote>
<pre wrap="">
I see no technical reason against it, but I wouldn't like it because
then the headers belonging to a module wouldn't be located in the module
anymore. Actions performed on a module would need to take that
additional inc path into account, for example grep, module local tags
and ID databases, and maybe more. Doxygen?
Eike
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
LibreOffice mailing list
<a class="moz-txt-link-abbreviated" href="mailto:LibreOffice@lists.freedesktop.org">LibreOffice@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/libreoffice">http://lists.freedesktop.org/mailman/listinfo/libreoffice</a>
</pre>
</blockquote>
<br><br><br><hr><font size="-2" color=808080>Disclaimer: <a href="http://www.peralex.com/disclaimer.html">http://www.peralex.com/disclaimer.html</a><br><br>
</body>
</html>