Guillaume Munch wrote:
Then, I must translate for people who do not read French. Essentially,
if the plan is to use c++11 features starting from 2.3, and 2.2 requires
c++98 compatibility, then backporting new code is going to involve
unusual efforts, or discourage using the features as long
PhilipPirrip wrote:
On 08/19/2015 04:44 PM, Georg Baum wrote:
PhilipPirrip wrote:
Why does \input@path end with two slashes, as in
/home/user/directory//
IIRC this means that also sub directories are searched, but this should
be documented in some TeX or LaTeX docs.
I did some reserach,
Why does \input@path end with two slashes, as in
/home/user/directory//
IIRC this means that also sub directories are searched, but this should
be documented in some TeX or LaTeX docs.
Not sure how it all works for (La)TeX, I'm assuming this is all handled
by the OS. Unixoids (OSX, Linux)
Guillaume Munch wrote:
> Then, I must translate for people who do not read French. Essentially,
> if the plan is to use c++11 features starting from 2.3, and 2.2 requires
> c++98 compatibility, then backporting new code is going to involve
> unusual efforts, or discourage using the features as
PhilipPirrip wrote:
> On 08/19/2015 04:44 PM, Georg Baum wrote:
>> PhilipPirrip wrote:
>>
>>> Why does \input@path end with two slashes, as in
>>> /home/user/directory//
>>
>> IIRC this means that also sub directories are searched, but this should
>> be documented in some TeX or LaTeX docs.
I
Why does \input@path end with two slashes, as in
/home/user/directory//
IIRC this means that also sub directories are searched, but this should
be documented in some TeX or LaTeX docs.
Not sure how it all works for (La)TeX, I'm assuming this is all handled
by the OS. Unixoids (OSX, Linux)
