Marcos Douglas escreveu:
On Tue, Jun 8, 2010 at 12:55 PM, Luiz Americo Pereira Camara
wrote:
Marcos Douglas escreveu:
Hi Luiz,
On Mon, Jun 7, 2010 at 10:35 PM, Luiz Americo Pereira Camara
wrote:
Take a look at
http://lazarusroad.blogspot.com/2008/11/effect-of-using-constant
On Tue, Jun 8, 2010 at 12:55 PM, Luiz Americo Pereira Camara
wrote:
> Marcos Douglas escreveu:
>>
>> Hi Luiz,
>>
>> On Mon, Jun 7, 2010 at 10:35 PM, Luiz Americo Pereira Camara
>> wrote:
>>
>>>
>>> Take a look at
>>>
>>> http://lazarusroad.blogspot.com/2008/11/effect-of-using-constant-parameter-f
Hi all,
On the 26th of june there is a meeting for the Lazarus and Freepascal
developers in the Netherlands. The developers who have time and the
possibility to come to the Netherlands will be there, to see each other
in the 'real world'. And to discuss ideas and new developments around
Freepascal
Hello FPC-Pascal,
Tuesday, June 8, 2010, 2:23:52 PM, you wrote:
>> I know, and tried both just too see. But as Jonas has said, FPC
>> itself uses
>> semi-colon on all platforms, hence the reason I tried semi-colon
>> first.
JM> The compiler should actually be changed to use the platform-specifi
Jonas Maebe schrieb:
because a directory on a unix platform can perfectly contain
a semi-colon.
That applies to Windows too.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Marcos Douglas escreveu:
Hi Luiz,
On Mon, Jun 7, 2010 at 10:35 PM, Luiz Americo Pereira Camara
wrote:
Take a look at
http://lazarusroad.blogspot.com/2008/11/effect-of-using-constant-parameter-for.html
Then, this continue true how I said in other mail:
On Mon, Jun 7, 2010 at 11:59 A
Hi Luiz,
On Mon, Jun 7, 2010 at 10:35 PM, Luiz Americo Pereira Camara
wrote:
>
> Take a look at
> http://lazarusroad.blogspot.com/2008/11/effect-of-using-constant-parameter-for.html
>
Then, this continue true how I said in other mail:
On Mon, Jun 7, 2010 at 11:59 AM, Marcos Douglas wrote:
> Al
Op 2010-06-08 14:23, Jonas Maebe het geskryf:
>
> The compiler should actually be changed to use the platform-specific
> separator, because a directory on a unix platform can perfectly
> contain a semi-colon.
I guess, but do you really want to go down that route? :-) Linux (and
probably othe
On 08 Jun 2010, at 14:16, Graeme Geldenhuys wrote:
I know, and tried both just too see. But as Jonas has said, FPC
itself uses
semi-colon on all platforms, hence the reason I tried semi-colon
first.
The compiler should actually be changed to use the platform-specific
separator, because a
Op 2010-06-08 13:26, Michael Van Canneyt het geskryf:
>
> No. You must specify a -Fi per path. It doesn't split the path.
Umm, but FPC allows it in fpc.cfg file, so maybe allowing it in fpdoc will
be more consistent don't you think. It should be rather easy to add.
eg:
A sample from FPC generate
On 08 Jun 2010, at 13:26, Michael Van Canneyt wrote:
No. You must specify a -Fi per path. It doesn't split the path.
(coincidentally, the path separator is : on linux, not ; :))
At least for the fpc/ppcXXX binaries, the path separator is ";" on all
platforms.
Jonas
__
On Tue, 8 Jun 2010, Graeme Geldenhuys wrote:
Hi
Is fpdoc supposed to handle multiple include paths with one -Fi parameter?
eg:
--input='-Fi../src/corelib;../src/corelib/x11
../src/corelib/fpg_utils.pas' --descr=xml/corelib/fpg_utils.xml \
The above line fails. fpdoc cannot find the inclu
Hi
Is fpdoc supposed to handle multiple include paths with one -Fi parameter?
eg:
--input='-Fi../src/corelib;../src/corelib/x11
../src/corelib/fpg_utils.pas' --descr=xml/corelib/fpg_utils.xml \
The above line fails. fpdoc cannot find the include file used my
fpg_utils.pas unit. Changing that
Here is another parser error causing fpdoc to fail generating documentation.
http://bugs.freepascal.org/view.php?id=16673
--
Regards,
- Graeme -
___
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/
_
fpdoc or fcl-passrc seems to be worse of than it was before. I know
fcl-passrc was going to be modified for fpdoc, so it only parses the
interface section. But the code listed in the bug report IS in the
interface section. It can't seem to parse a class definition that
contains the 'platform' hi
15 matches
Mail list logo