Op 2010-08-26 21:17, Marco van de Voort het geskryf:
What is the pos() case meant to solve? If relative link starts with the
current modules unit name, then try package.relativelink?
I did some tests and compared output files generated. I only found 4
incorrectly resolved links in the
Hi
In the case of Classes unit documentation - more specifically the TThread
documentation. The default behaviour when making RTL documentation, is for
it to hide/exclude the protected section from the docs.
This includes the TThread.Execute and TThread.Synchronize methods, which
actually has
On Fri, 27 Aug 2010, Graeme Geldenhuys wrote:
Hi
In the case of Classes unit documentation - more specifically the TThread
documentation. The default behaviour when making RTL documentation, is for
it to hide/exclude the protected section from the docs.
This includes the TThread.Execute and
In our previous episode, Graeme Geldenhuys said:
What is the pos() case meant to solve? If relative link starts with the
current modules unit name, then try package.relativelink?
I did some tests and compared output files generated. I only found 4
incorrectly resolved links in the current
On Fri, 27 Aug 2010, Marco van de Voort wrote:
In our previous episode, Graeme Geldenhuys said:
What is the pos() case meant to solve? If relative link starts with the
current modules unit name, then try package.relativelink?
I did some tests and compared output files generated. I only
Am 27.08.2010 13:11, schrieb Michael Van Canneyt:
On Fri, 27 Aug 2010, Graeme Geldenhuys wrote:
Hi
In the case of Classes unit documentation - more specifically the TThread
documentation. The default behaviour when making RTL documentation, is
for
it to hide/exclude the protected section
On Fri, 27 Aug 2010, Sven Barth wrote:
Am 27.08.2010 13:11, schrieb Michael Van Canneyt:
On Fri, 27 Aug 2010, Graeme Geldenhuys wrote:
Hi
In the case of Classes unit documentation - more specifically the TThread
documentation. The default behaviour when making RTL documentation, is
for
Am 27.08.2010 13:40, schrieb Michael Van Canneyt:
On Fri, 27 Aug 2010, Sven Barth wrote:
Am 27.08.2010 13:11, schrieb Michael Van Canneyt:
On Fri, 27 Aug 2010, Graeme Geldenhuys wrote:
Hi
In the case of Classes unit documentation - more specifically the
TThread
documentation. The
Op 2010-08-27 13:16, Marco van de Voort het geskryf:
Did you compare html?
Yes, but I used fpGUI documentation only. For RTL, FCL I used LaTex and IPF
output.
Could you btw explain the logic behind the canweexit hack? I don't fully
understand why underscores are now equal to points. Won't
Op 2010-08-27 13:32, Michael Van Canneyt het geskryf:
Maybe. But it seems to effectively disable module.identifier resolution
(for modulecurrentmodule). So while it may not be the most used
functionality, the question is why it must be (effectively) removed.
It was never supported in the
In our previous episode, Graeme Geldenhuys said:
Yes, but I used fpGUI documentation only. For RTL, FCL I used LaTex and IPF
output.
I'll have to digest your and Michael msgs and check all ends first before I
can reply in any sane way.
Till now, I fixed that routine also in a drive-by style,
On 2010-08-26 17:24, Graeme Geldenhuys wrote:
I'll find it a new home tomorrow and post the link
Any news? ;)
Regards
Žilvinas
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
2010/8/27 Žilvinas Ledas:
I'll find it a new home tomorrow and post the link
Any news? ;)
Yes, I placed in on GitHub. You can clone the repository as follows:
via git protocol (faster):
git clone git://github.com/graemeg/fpprofiler.git
via http protocol:
git clone
I got a strange error while compiling, saying that fpc couldn't open
the fpc.cfg file (sorry lost the exact wording)
The file definitely was/is there. And on repeated compilation all worked
fine.
Only thing I can think off: I was compiling to different projects. The
projects where
14 matches
Mail list logo
