Thank you for answer JJ.
It is quite a work to split such a large file up so I thought I'd better
ask before I dive in head first. Later I might think it over. I have
this documentation on the github pages too so I could separate the pod
doc and keep them somewhere else where they won't get processed and
installed.
Thanks again,
Marcel
It's going to be pretty much the same. If it's installed, it's going
to be precompiled anyway. The overhead added by reading the file might
even make it slower.
Of course, you can always give it a try and measure. Measuring might
always surprise you :-)
El mar., 14 jul. 2020 a las 14:20, Marcel Timmerman (<mt1...@gmail.com
<mailto:mt1...@gmail.com>>) escribió:
Hi,
I was wondering if pod documentation has a large impact on compiling
modules. I assume on small files it would be ignorable but I have
some
modules which have grown big, one has 7153 lines of which the biggest
part is pod doc. Would it be useful to split such a file in two.
one for
code and the other for doc to improve the install time?
Regards,
Marcel
--
JJ
