On 02/11/16 12:53, Tony Whyman wrote:
There was a certain amount of sarcasm in my comment that perhaps got
lost in translation. I suggested introducing a "delphi with bugs" mode
to illustrate the absurdity of the idea. My point is that why should FPC
still feel constrained by Delphi? Let's get on
On 02/11/16 11:29, Jonas Maebe wrote:
On 02/11/16 12:09, Tony Whyman wrote:
It's an interesting concept i.e. if a bug exists in Delphi then it must
also exist in FPC. Perhaps a better alternative is to fix these sort of
bugs in FPC and to introduce a "full Dephi compatibility mode" i.e.
mode De
On 02/11/16 12:09, Tony Whyman wrote:
It's an interesting concept i.e. if a bug exists in Delphi then it must
also exist in FPC. Perhaps a better alternative is to fix these sort of
bugs in FPC and to introduce a "full Dephi compatibility mode" i.e.
mode Delphi plus the bugs.
There is a differ
On 2016-11-02 11:32, Dennis wrote:
> How can I do the same in FPC?
You can take a look at tiOPF's tiSemaphore.pas unit in the 'tiopf2'
branch. tiOPF source code is hosted on SourceForge.net
Regards,
Graeme
___
fpc-pascal maillist - fpc-pascal@lists
If a CriticalSection can acquire (but with a timeout), it can avoid any
gridlock.
I googled and Delphi seems to have function which does time out
function MonitorEnter(const AObject: TObject; Timeout: Cardinal =
INFINITE): Boolean; How can I do the same in FPC? Dennis
It's an interesting concept i.e. if a bug exists in Delphi then it must
also exist in FPC.
Yes I agree. FPC's Interfaces support suffer the same fate. eg: FPC's
CORBA style interfaces which Delphi doesn't have, implements the same
bugs as Delphi COM Interfaces???
I would prefer FPC to be bug f
On 2016-11-02 11:09, Tony Whyman wrote:
> It's an interesting concept i.e. if a bug exists in Delphi then it must
> also exist in FPC.
Yes I agree. FPC's Interfaces support suffer the same fate. eg: FPC's
CORBA style interfaces which Delphi doesn't have, implements the same
bugs as Delphi COM Int
It's an interesting concept i.e. if a bug exists in Delphi then it must
also exist in FPC. Perhaps a better alternative is to fix these sort of
bugs in FPC and to introduce a "full Dephi compatibility mode" i.e.
mode Delphi plus the bugs.
On 02/11/16 11:04, Gabor Boros wrote:
2016. 11. 02.
2016. 11. 02. 11:38 keltezéssel, Michael Van Canneyt írta:
If Delphi prints another result, then we can look at fixing the
implementation.
With Delphi 10.1 and "D: TDate;" the result is "date is 5" and with "D:
TDateTime;" the result is "date is 7". So, the results are same with FPC
and Delph
Dňa 2.11.2016 o 11:38 Michael Van Canneyt napísal(a):
On Wed, 2 Nov 2016, Gabor Boros wrote:
Hi All,
I use MWA's IBX for Firebird connection and have problem with date
parameters. Tony provided to me a test program a suggested write to
the FPC list. The simple test program is:
program Pr
On Wed, 2 Nov 2016, Gabor Boros wrote:
Hi All,
I use MWA's IBX for Firebird connection and have problem with date
parameters. Tony provided to me a test program a suggested write to the FPC
list. The simple test program is:
program Project1;
uses Variants, Sysutils;
var V: variant;
D
Hi All,
I use MWA's IBX for Firebird connection and have problem with date
parameters. Tony provided to me a test program a suggested write to the
FPC list. The simple test program is:
program Project1;
uses Variants, Sysutils;
var V: variant;
D: TDate;
begin
D := EncodeDate(2016,10,
12 matches
Mail list logo
