QFT, Flávio said:
"Graeme, I guess the OP didn't want to reintroduce the 'Create'
constructor with lower visibility, just implement a second constructor
(** with a different name **) with private visiblity. It can be useful
when implementing singletons and factories to avoid some types of
misuse b
On Tue, Nov 10, 2009 at 10:56 AM, Graeme Geldenhuys
wrote:
> Anthony Walter wrote:
>>
>> In my opinion the warning should be removed, or at least able to be
>> suppress through a switch. I beginning to make the transition to cross
>
> The compiler is 100% and I think it should actually raise an Er
Hi
Is there a way (or a 3rd party component or a library) to catch an endless
loop after x seconds
in applications running on arm Wince?
--
View this message in context:
http://old.nabble.com/Any-Way-to-catch-endless-loop-in-fpc-in-Wince--tp26293620p26293620.html
Sent from the Free Pascal - Gen
Sorry, Create is an identifier.
constructor TSampleForm.Create(AOwner: TComponent);
var
Create: Integer;
begin
inherited;
Create := Tag;
Caption := IntToStr(Create);
end;
Aside from that, if you read you will see I used two identifiers ...
one called "Create" and another called ... get th
- Original Message -
From: "Anthony Walter"
To: ; "FPC-Pascal users discussions"
Sent: Wednesday, November 11, 2009 1:07 AM
Subject: Re: [fpc-pascal] Compiler Warning: Constructor should be public
Your argument is flawed. Visibility rules apply to identifiers, not
keywords.
Create
indent can only add or delete whitespace. Comments that start with //
and extend beyond the -lcn limit are left alone.
Henry Vermaak wrote:
2009/11/10 Wimpie Nortje :
Ok, I've tried indent and it doesn't do the job because the comments are
also 400 chars long.
>From indent man page:
2009/11/10 Wimpie Nortje :
> Ok, I've tried indent and it doesn't do the job because the comments are
> also 400 chars long.
>From indent man page:
-ln, --line-lengthn
Set maximum line length for non-comment lines to n.
See BREAKING LONG LINES.
-lcn, --comment-line-lengthn
Set maximum
Ok, I've tried indent and it doesn't do the job because the comments are
also 400 chars long.
I also tried to add {$H+} to the top of h2pas.pas but the solution is
not that easy.
If someone could give me a pointer of where to start, maybe I can try to
fix it. For starters, what is the yacc a
Thanks, I will try that.
Henry Vermaak wrote:
2009/11/10 Wimpie Nortje :
Hallo
I am trying to convert a .h to pascal with h2pas. The header file contains
many declarations with lines of 400 characters or longer. h2pas creates the
*.tmp.h file with all the code intact but the .pas file's lin
2009/11/10 Wimpie Nortje :
> Hallo
>
> I am trying to convert a .h to pascal with h2pas. The header file contains
> many declarations with lines of 400 characters or longer. h2pas creates the
> *.tmp.h file with all the code intact but the .pas file's lines are cut off
> at 256 characters. Is there
Hallo
I am trying to convert a .h to pascal with h2pas. The header file
contains many declarations with lines of 400 characters or longer. h2pas
creates the *.tmp.h file with all the code intact but the .pas file's
lines are cut off at 256 characters. Is there an easy way around this
problem,
Your argument is flawed. Visibility rules apply to identifiers, not keywords.
Create // identifier
CreateFromLine // different identifier
No visibility is being changed by introducing a *new* identifier
raise EAssertError.Create(Msg); // still visible
raise EAssertError.CreateFromLine(Msg, FileN
Anthony Walter wrote:
>
> In my opinion the warning should be removed, or at least able to be
> suppress through a switch. I beginning to make the transition to cross
The compiler is 100% and I think it should actually raise an Error
instead of a Warning.
Your code is flawed. Object Pascal is qu
On 10 Nov 2009, at 14:35, Anthony Walter wrote:
In my opinion the warning should be removed, or at least able to be
suppress through a switch.
FPC 2.4.0 will include the ability to suppress individual messages.
Use -vq to show the messages numbers, and -vm to suppress a
particular message
I've searched the list archives related to the subject of the fpc
warning "Constructor should be public" and am unsure as to the
resolution of this issue, or would perhaps like to revisit it.
In my opinion the warning should be removed, or at least able to be
suppress through a switch. I beginning
Dimitrios Chr. Ioannidis schreef:
Hi,
Is the 32 bit gdb in
http://svn.freepascal.org/svn/fpcbuild/trunk/install/binw32 able to
debug reliably a 64 bit process ?
AFAIK you cannot use the 32 bits version.
You can download gdb for win64 from SF. A tested version (but not the latest
version)
Hi,
i have build a native ppcx64 in windows 7 64 bit. But i can't find a 64
bit version of GDB in
http://svn.freepascal.org/svn/fpcbuild/trunk/install/binw64.
Is the 32 bit gdb in
http://svn.freepascal.org/svn/fpcbuild/trunk/install/binw32 able to
debug reliably a 64 bit process ? Or i must
17 matches
Mail list logo
