2011/12/16 Jonas Maebe :
> Inline is not a calling convention, nor does it affect the calling convention.
You are right, its not a calling convention and declaring a different
convention in the implementation indeed does not work.
But I am still surprised that inline can be declared in either of
On 17 Dec 2011, at 11:29, Bernd wrote:
> But I am still surprised that inline can be declared in either of the
> two sections ( I am not complaining, I am actually glad it works for
> my particular application). Is there any recommended style, is it bad
> practice to put it into the implementatio
- Original Message -
> From: Michael Van Canneyt
> To: FPC-Pascal users discussions
> Cc: Lazarus mailing list
> Sent: Friday, December 16, 2011 5:52 PM
> Subject: Re: [fpc-pascal] JSON Dataset in FCL-DB.
>
>
>
> On Fri, 16 Dec 2011, Leonardo M. Ramé wrote:
>
>>> What is missing cu
- Original Message -
> From: Leonardo M. Ramé
> To: FPC-Pascal users discussions
> Cc:
> Sent: Saturday, December 17, 2011 10:00 AM
> Subject: Re: [fpc-pascal] JSON Dataset in FCL-DB.
>
> - Original Message -
>
>> From: Michael Van Canneyt
>> To: FPC-Pascal users discussion
On Sat, 17 Dec 2011, Leonardo M. Ramé wrote:
- Original Message -
From: Michael Van Canneyt
To: FPC-Pascal users discussions
Cc: Lazarus mailing list
Sent: Friday, December 16, 2011 5:52 PM
Subject: Re: [fpc-pascal] JSON Dataset in FCL-DB.
+
P.ExamplePath.Add('tests');
On Sat, 17 Dec 2011, Leonardo M. Ramé wrote:
- Original Message -
Also this on tests directory:
Index: testjsondataset.pp
===
--- testjsondataset.pp (revision 19860)
+++ testjsondataset.pp (working copy)
@@ -3,9 +3,8
The article is very good, but it does not focuse on all aspects.
I have tried to create my first test example, but it didn't work. The
compilation is successful and the program is executed without errors.
However, I received no messages, informing the test has failed.
Actually, the test should
You see no test results, because the program file of your test
application is missing some essential things.
If you are using lazarus, simply create a new testing application:
First, make sure that package fpcunitide is installed.
Then, in the 'File-New' dialog, your testproject should be of
Michael,
I have a meaningful peculiarity: I am blind and I use Freepascal only in
the console interface, reading all the output by means of my screen
reader. Lazarus and Freepascal console IDE are both inaccessible. But,
fortunately, for me, it's easy to call the compiler passing parameters
a
On Sat, Dec 17, 2011 at 5:03 PM, Luciano de Souza wrote:
> I can compile using callings like:
> fpc test.pas
> fpc -XX test.pas
> fpc test.pas -Fu./pas -FE./exe
You can compile Lazarus projects in the command line using lazbuild
which comes with Lazarus, like this:
lazbuild project.lpi
It will
I used generics in Lazarus code base for the first time, in TreeFilter
component:
TTreeNodeList = specialize TFPGList;
and
TBranchList = specialize TFPGObjectList;
I works for me on Windows and Linux, with FPC 2.4.4 and 2.6.0 RC1.
Now Zeljan reported it does not compile on Mac OSX 64-bit, usi
2011/12/17 Juha Manninen
> I used generics in Lazarus code base for the first time, in TreeFilter
> component:
>
> TTreeNodeList = specialize TFPGList;
> and
> TBranchList = specialize TFPGObjectList;
>
> I works for me on Windows and Linux, with FPC 2.4.4 and 2.6.0 RC1.
> Now Zeljan reported
On 17 Dec 2011, at 18:22, Juha Manninen wrote:
> "Fatal: Syntax error, ">" expected but "CLASS" found"
>
> Works on 64-bit Linux.
> How can OSX affect generics syntax?
There are no Mac OS X-specific failures of generics tests in the testsuite (64
bit or otherwise, Intel or PowerPC). There are
2011/12/17 Jonas Maebe
>
> On 17 Dec 2011, at 18:22, Juha Manninen wrote:
>
> > "Fatal: Syntax error, ">" expected but "CLASS" found"
> >
> > Works on 64-bit Linux.
> > How can OSX affect generics syntax?
>
> There are no Mac OS X-specific failures of generics tests in the testsuite
> (64 bit or
On Sat, 17 Dec 2011 17:47:49 +0100
Felipe Monteiro de Carvalho wrote:
> On Sat, Dec 17, 2011 at 5:03 PM, Luciano de Souza wrote:
> > I can compile using callings like:
> > fpc test.pas
> > fpc -XX test.pas
> > fpc test.pas -Fu./pas -FE./exe
>
> You can compile Lazarus projects in the command li
You would believe if I told you I could not compile yet?
It's not lack of effort, believe me. I really can't understand what is
failing.
See my compilation script:
@echo off
set compilerpath="c:\lazarus\fpc\2.4.4\bin\i386-win32\fpc.exe"
set unitpath="-Fuc:\lazarus\fpc\units\i386-win32\*
-Fuc
two little questions
1. Is it possible to make an alias to a function ... so rather than just
re-calling with the same parameters, it's actually the same thing? like the way
we can do, e.g., type natural = cardinal, or const GG = 6, but with a function?
2. is it possible to overload the 'in' op
17 matches
Mail list logo
