ABorka schreef:
BTW, there should be some explanation in Lazarus - File - New for
people about the differences between
Application - Program - Custom Program ;
I think the description in the Project - New ... explains the
differences clear enough.
If not, what are you missing?
Vincent
On Wed, 10 Jun 2009, Martin wrote:
Procedures/Functions can have default values for arguments, so they don't
need to be specified if called
function GetFoo(Bar: integer; XY: Boolean = True): Integer;
Properties (indexed) don't have such a syntax:
property Foo[Bar: integer; XY: Boolean =
Hi.
I extend my patch for suppressing compiler messages. Now it is possible
to remap compiler message verbosity by command parametr:
-vm5024_,5025w,5026e which means:
suppress message 5024, 5025 is warning and 5026 is error
-vq shows compiler message numbers
Is better to send extension patches
Op woensdag 10-06-2009 om 17:19 uur [tijdzone -0700], schreef ABorka:
Adding fcgi-support was only two hours work. Other systems can be added
as wel. Next on my list is a native web-server using lnet, so that
debugging is even easier. (I'm absolutely sure that posting all messages
about
Michael Van Canneyt wrote:
On Wed, 10 Jun 2009, Martin wrote:
However the follwing Syntax compiles fine:
function GetFoo(Bar: integer; XY: Boolean = True): Integer;
property Foo[Bar: integer; XY: Boolean] read GetFoo;
a := Object.Foo[1];
But:
Is that supposed to work?
No, it is not. It is a
Op donderdag 11-06-2009 om 14:04 uur [tijdzone +0200], schreef
petr.kris...@epos.cz:
I extend my patch for suppressing compiler messages. Now it is possible
to remap compiler message verbosity by command parametr:
-vm5024_,5025w,5026e which means:
suppress message 5024, 5025 is warning and
On Thu, Jun 11, 2009 at 02:15:15PM +0200, Joost van der Sluis wrote:
Op donderdag 11-06-2009 om 14:04 uur [tijdzone +0200], schreef
petr.kris...@epos.cz:
I extend my patch for suppressing compiler messages. Now it is possible
to remap compiler message verbosity by command parametr:
On 11 Jun 2009, at 14:14, Martin Friebe wrote:
However it would be nice to have a feature like
property Foo[Index: Integer]: Integer write SetFoo read GetFoo;
property Foo[Index: Integer; Ask: Boolean]: Integer write
SetFooAsk read GetFooAsk;
The must have different Method Names,
On Thu, 11 Jun 2009, Jonas Maebe wrote:
On 11 Jun 2009, at 14:14, Martin Friebe wrote:
However it would be nice to have a feature like
property Foo[Index: Integer]: Integer write SetFoo read GetFoo;
property Foo[Index: Integer; Ask: Boolean]: Integer write SetFooAsk
read GetFooAsk;
On 11 Jun 2009, at 14:44, Michael Van Canneyt wrote:
On Thu, 11 Jun 2009, Jonas Maebe wrote:
On 11 Jun 2009, at 14:14, Martin Friebe wrote:
However it would be nice to have a feature like
property Foo[Index: Integer]: Integer write SetFoo read GetFoo;
property Foo[Index: Integer; Ask:
On Thu, 11 Jun 2009, Jonas Maebe wrote:
On 11 Jun 2009, at 14:44, Michael Van Canneyt wrote:
On Thu, 11 Jun 2009, Jonas Maebe wrote:
On 11 Jun 2009, at 14:14, Martin Friebe wrote:
However it would be nice to have a feature like
property Foo[Index: Integer]: Integer write SetFoo read
Op Thu, 11 Jun 2009, schreef Michael Van Canneyt:
On Thu, 11 Jun 2009, Jonas Maebe wrote:
I would think it is a natural extension of procedural overloading ?
It's not that simple. Properties can be both hidden variable access as
well as procedure access. Variable overloading is not
On Thu, 11 Jun 2009, Daniël Mantione wrote:
Op Thu, 11 Jun 2009, schreef Michael Van Canneyt:
On Thu, 11 Jun 2009, Jonas Maebe wrote:
I would think it is a natural extension of procedural overloading ?
It's not that simple. Properties can be both hidden variable access as well
as
Daniël Mantione wrote:
Op Thu, 11 Jun 2009, schreef Michael Van Canneyt:
On Thu, 11 Jun 2009, Jonas Maebe wrote:
I would think it is a natural extension of procedural overloading ?
It's not that simple. Properties can be both hidden variable access as
well as procedure access. Variable
Well, this is just my opinion - maybe others could say something too -
but I think it would clear up things a bit if we do the following things:
1. I think all the Custom variations should be removed it just
confuses new arrival people.
Any pro will know how to make those anyway.
Or make the
15 matches
Mail list logo
