Am 02.07.2015 um 12:37 schrieb Serguei TARASSOV:
>
> Be honest, I have doubts about "Pascal spirit" of this genre.
FPC tries to support all flavours of pascal, even ISO. If you are
interested only in one flavour, just add the appropriate mode switch to
your config and be done. If FPC limited itse
Serguei TARASSOV wrote on Thu, 02 Jul 2015:
Object type can be used as "advanced record" in FPC mode only.
I'm agreed that it is good evolution since turbo pascal.
But in Delphi mode you cannot use object type in a same manner (i.e.
for operator overloading) and then should use advanced record
On 02/07/2015 10:32, fpc-pascal-requ...@lists.freepascal.org wrote:
Date: Wed, 1 Jul 2015 17:51:43 +0200
From: Jonas Maebe
To: FPC-Pascal users discussions
Subject: Re: [fpc-pascal] Delphi mode for new features?
The point is that we consider that several features added by Embarcadero
make the
On 07/01/2015 05:40 PM, Serguei TARASSOV wrote:
Are you agreed that more FPC is compatible with Delphi "by default",
more users can use it without troubles and learning additional docs?
Delphi is getting so horribly expensive (without noticeable benefit)
that the user base is going to shrink dr
On 07/01/2015 05:51 PM, Jonas Maebe wrote:
The point is that we consider that several features added by
Embarcadero make the language less Pascal-like or more complicated for
no good reason. "Advanced records" is one such example: that feature
already existed, and is called "objects" or "Turbo
On 2015-07-01 16:47, Michael Van Canneyt wrote:
> If you want to use these features all the time, just put them in your config
> file.
+1
And we all know Embarcadero so often _copy really bad ideas_ from other
languages - giving no thought to the beauty and structure of the Object
Pascal languag
On 01/07/15 17:40, Serguei TARASSOV wrote:
> On 01/07/2015 17:08, fpc-pascal-requ...@lists.freepascal.org wrote:
>>
>> Such new Delphi features are only enabled by default in FPC modes if
>> we consider them to not run counter to the spirit of Pascal. That's
>> obviously subjective, but so is Embar
On Wed, 1 Jul 2015, Serguei TARASSOV wrote:
and disabled via mode switches.
This is a good example of complicating the life.
"One option by feature" to activate every new language feature lead to growth
of end-user documentation and using $MODE DELPHI when it is not required at
all.
In th
On 01/07/2015 17:08, fpc-pascal-requ...@lists.freepascal.org wrote:
Date: Wed, 01 Jul 2015 16:54:30 +0200
From: Jonas Maebe
To: FPC-Pascal users discussions
Subject: Re: [fpc-pascal] Delphi mode for new features?
Message-ID:
<20150701165430.horde.fbbhakisjlfvk-8mg
On 2015-07-01 15:54, Jonas Maebe wrote:
> all new language features we add these days can be selectively enabled
> and disabled via mode switches.
That was/is a very good decision, and makes it quite flexible per project.
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit u
Serguei TARASSOV wrote on Wed, 01 Jul 2015:
As I see (may be mistaken), some _new_ Delphi features are available
only in $MODE DELPHI.
This way lead to divergence of two compilers.
Why do not implement them in FPC "by default" (when it not
constrained by basic concepts and legacy code) to
Hi All,
My question is inspired by some things asked here last weeks.
As I see (may be mistaken), some _new_ Delphi features are available
only in $MODE DELPHI.
This way lead to divergence of two compilers.
Why do not implement them in FPC "by default" (when it not constrained
by basic concep
On 19 Jan 2010, at 15:14, Marco van de Voort wrote:
Hmm, under delphi at least, it is cheaper to do
var pstart,pend : PSomeType;
if length(sometypedynarray)>0 then
begin
pstart:=...@sometypedynarray[0];
peind :=...@sometypedynarray[length(sometypedynarray)-1];
while (pstart<=peind)
In our previous episode, Jonas Maebe said:
> I also don't see any advantage to using a pointer instead of a dynamic
> array directly. It will not be faster in any way, since there are no
> uniqueness checks for dynamic arrays. In fact, it will probably be
> slower, since you now have two vari
On 19 Jan 2010, at 14:39, Roland Turcan wrote:
<<< 19.01.2010 13:10 - Jonas Maebe "jonas.ma...@elis.ugent.be" >>>
JM> Oops, only now I see he was trying to index a pointer like an
array.
JM> And even in FPC I would very strongly recommend against
typecasting a
JM> dynamic array to a pointe
<<< 19.01.2010 13:10 - Jonas Maebe "jonas.ma...@elis.ugent.be" >>>
JM> On 19 Jan 2010, at 12:57, Michael Van Canneyt wrote:
>> It should not compile in Delphi mode.
>> Array syntax is not supported by Delphi.
JM> Oops, only now I see he was trying to index a pointer like an array.
JM> And even
On 19 Jan 2010, at 12:57, Michael Van Canneyt wrote:
It should not compile in Delphi mode.
Array syntax is not supported by Delphi.
Oops, only now I see he was trying to index a pointer like an array.
And even in FPC I would very strongly recommend against typecasting a
dynamic array to a
On Tue, 19 Jan 2010, Roland Turcan wrote:
<<< 19.01.2010 11:39 - Jonas Maebe "jonas.ma...@elis.ugent.be" >>>
JM> On 19 Jan 2010, at 11:27, Jonas Maebe wrote:
On 19 Jan 2010, at 11:14, Roland Turcan wrote:
ShowMessage (IntToStr (MyItems[0]));
I think this should work:
ShowMessage (IntTo
<<< 19.01.2010 11:39 - Jonas Maebe "jonas.ma...@elis.ugent.be" >>>
JM> On 19 Jan 2010, at 11:27, Jonas Maebe wrote:
>> On 19 Jan 2010, at 11:14, Roland Turcan wrote:
>>
>>> ShowMessage (IntToStr (MyItems[0]));
>>
>> I think this should work:
>> ShowMessage (IntToStr (MyItems[0]()));
>>
>> Please
On 19 Jan 2010, at 11:27, Jonas Maebe wrote:
On 19 Jan 2010, at 11:14, Roland Turcan wrote:
ShowMessage (IntToStr (MyItems[0]));
I think this should work:
ShowMessage (IntToStr (MyItems[0]()));
Please also file a bug report with a compilable example (which does
not depend on Lazarus) th
On 19 Jan 2010, at 11:14, Roland Turcan wrote:
I use Delphi style of programing in Lazarus to keep a compatibility
with Kylix and therefore I want to get this code which is valid of
Freepascal's ObjectPascal, but in {$MODE Delphi} it doesn't accept
calling of "MyItems[index]" and writes "Array
Hello all,
I use Delphi style of programing in Lazarus to keep a compatibility
with Kylix and therefore I want to get this code which is valid of
Freepascal's ObjectPascal, but in {$MODE Delphi} it doesn't accept
calling of "MyItems[index]" and writes "Array type required".
How to adapt this code
Carsten Bager wrote:
Is there another way writing this without activating Delphi mode.
Carsten
type
tKeypressed=function:boolean;
Var
pKeypressed:tKeypressed;
Function Keypressed:boolean;
Implementation
Function Keypressed:boolean;
Begin
if pointer(pKeypressed)<>nil then
Keypressed:
Is there another way writing this without activating Delphi mode.
Carsten
type
tKeypressed=function:boolean;
Var
pKeypressed:tKeypressed;
Function Keypressed:boolean;
Implementation
Function Keypressed:boolean;
Begin
if pointer(pKeypressed)<>nil then
Keypressed:=pKeypressed
else
Carsten Bager wrote:
Why do I have to use the {$MODE Delphi} directive to compile this,
It compiles in TP 6
-
Type
tFun=function:boolean;
Procedure g(f:tFun);
Begin
if f then exit;
End;
--
Because f is a function variable and not the result. In Delphi it can
On 2 feb 2006, at 16:10, Carsten Bager wrote:
Why do I have to use the {$MODE Delphi} directive to compile this,
It compiles in TP 6
You can also use {$mode tp} (and you should if you are compiling TP
code).
-
Type
tFun=function:boolean;
Procedure g(f:tFun);
Begin
if f th
Why do I have to use the {$MODE Delphi} directive to compile this,
It compiles in TP 6
-
Type
tFun=function:boolean;
Procedure g(f:tFun);
Begin
if f then exit;
End;
--
I ask because when I am in Delphi mode this can not compile
Var
tekster:Tekster_typ; external
27 matches
Mail list logo
