Hello,
I am having momentarily confusion about the situation with ccharset.pas and
charset.pas and strings, ansistrings and unicode in general... ?!?
So some questions about this:
I in particularly do not understand the following uses clausule:
{$ifdef VER2_2}ccharset{$else VER2_2}charset{$e
Hello,
File "cpubase.pas" in compiler subfolder 'x86' contains following comment:
"Contains the base types for the i386 and x86-64 architecture"
So I guess both folders are needed to build i386 target...
I will try that and see how it goes ;)
Bye,
Skybuck.
- Original Message -
From
Hello,
I have a little question about these subfolders in the compiler folder, they
are called:
'i386' and 'x86'
What are these folders, they seem samiliar ?
(cpubase.pas seems to be missing from i386 instead there is an include file
called cpubase.inc)
I'm a bit confused about these fold
On 5/4/2011 04:38, michael.vancann...@wisa.be wrote:
On Tue, 5 Apr 2011, LacaK wrote:
--or--
introduce any new method (ValidateFieldData ? ;-))) and let tdatsset
descendants use it:
{$IFDEF FPC}
ValidateFieldData(Field: TField; Buffer: Pointer);
{$ENDIF}
--or--
some smarter solution ?
On 05.04.2011 17:34, Sven Barth wrote:
- Is ibsymtableoptions needed? Couldn't be the value just be written to
the ppu without a new entry?
It didn't work the first time I added that, but it might be because of
other errors I had at that time. I'll recheck that to be sure.
I now remember why
The whole code, which is repeated (and can be put in one place) is:
if not (State in [dsEdit, dsInsert, dsFilter, dsCalcFields]) then
begin
DatabaseErrorFmt(SNotEditing,[Name],self);
exit;
end;
if (Field.FieldNo>0) and not (State in [dsSetKey, dsFilter]) then
begin
if Read
OnlythenDa
Am 05.04.2011 17:06, schrieb Florian Klaempfl:
Am 05.04.2011 04:27, schrieb Paul Ishenin:
I think your branch should be reviewed either by Florian
I did a quick review and found nothing important, only a few remarks:
- current_syssym: is it really needed? Can't the type checking be done
durin
Here is beginning and the end of today's snapshot make from zapped
directories and a new svn co - the whole thing is 13K zipped - you can have
it if you really want! J
C:/PP/BIN/WIN32/MAKE.EXE compiler_cycle RELEASE=1
MAKE.EXE[1]: Entering directory `D:/fpk'
C:/PP/BIN/WIN32/MAKE.EXE -C compi
Am 05.04.2011 04:27, schrieb Paul Ishenin:
>
> I think your branch should be reviewed either by Florian
I did a quick review and found nothing important, only a few remarks:
- current_syssym: is it really needed? Can't the type checking be done
during the type check pass? If it's needed, it shou
Skybuck Flying schrieb:
So I wonder what is involved in supporting a new platform... be it real
hardware or virtual machines.
One thing which comes to mind is the RTL ?
Do new "targets" (as it's called ?) require their own RTL as well ? I
did see a mention about a dummy RTL as a possibility
Skybuck Flying schrieb:
I would like to experiment with the pascal programming language at the
binary/assembler/machine level.
For example compile pascal sources to virtual machine instruction sets.
Only one machine (instruction set) is supported by an FPC executable.
This is because some c
On 05/04/2011 09:24, Joost van der Sluis wrote:
On Sun, 2011-04-03 at 21:11 +0100, Martin wrote:
On 03/04/2011 20:59, Martin wrote:
On 03/04/2011 20:50, Martin wrote:
(w32 / vista)
I tried to recompile fpc trunk, it starts up fine, until it comes to
fcl-web. I copied the last lines of output t
No, its the same win32 snapshot & method of doing it that I've been doing
every day for for years! not x compile. I just sent an extract from the log
asuming that it'd be obvious, as I've done for the errors I've had in the
past. I can send yoiu the whole log if you really need it.
I don't
Am 05.04.2011 11:42, schrieb dhkblas...@zeelandnet.nl:
On Tue, 05 Apr 2011 11:17:48 +0200, Sven Barth
wrote:
Am 05.04.2011 04:27, schrieb Paul Ishenin:
05.04.2011 3:51, Sven Barth wrote:
Both "class helpers" and "record helpers" are implemented and work as
Delphi compatible as reasonably pos
On Tue, 05 Apr 2011 11:17:48 +0200, Sven Barth
wrote:
Am 05.04.2011 04:27, schrieb Paul Ishenin:
05.04.2011 3:51, Sven Barth wrote:
Both "class helpers" and "record helpers" are implemented and work
as
Delphi compatible as reasonably possible.
Congratulations.
Thank you.
Just from my
Am 05.04.2011 11:17, schrieb Sven Barth:
Some notes regarding the tests:
* three record helper tests (trhlp*) fail, because nested types are not
supported by (advanced) records (two should fail nevertheless, because
they try to access (strict) private helpers, the third should succeed)
Nested t
Am 05.04.2011 04:27, schrieb Paul Ishenin:
05.04.2011 3:51, Sven Barth wrote:
Both "class helpers" and "record helpers" are implemented and work as
Delphi compatible as reasonably possible.
Congratulations.
Thank you.
Some notes regarding the tests:
* three record helper tests (trhlp*) f
Am 05.04.2011 10:19, schrieb Paul Ishenin:
05.04.2011 16:11, Florian Klaempfl wrote:
Yes, but but they need to be reviewed as well, no?
If they all were tested with delphi xe then no.
I developed them in Delphi XE first before I copied them into my branch.
(the only problem with my Starter
Am 05.04.2011 02:09, schrieb Skybuck Flying:
Hello,
I would like to experiment with the pascal programming language at the
binary/assembler/machine level.
For example compile pascal sources to virtual machine instruction sets.
I took a look at the free pascal sources and there seem to be some
Am 05.04.2011 07:21, schrieb Skybuck Flying:
Answering my own question ;)
I guess the answer to my question is more or less the same as the
following question:
"How to add a new target to free pascal compiler".
And I found this webpage which explains it a bit:
http://wiki.freepascal.org/Porti
Am 05.04.2011 09:38, schrieb Michael Schnell:
On 04/05/2011 02:21 AM, Skybuck Flying wrote:
So it would be cool if free pascal compiler could compile pascal
sources into redcode assembly, which can then be further compiled by
the PMARS executable/assembler.
AFAIK, other than gcc, FP is designed
On Sun, 2011-04-03 at 21:11 +0100, Martin wrote:
> On 03/04/2011 20:59, Martin wrote:
> > On 03/04/2011 20:50, Martin wrote:
> >> (w32 / vista)
> >> I tried to recompile fpc trunk, it starts up fine, until it comes to
> >> fcl-web. I copied the last lines of output to the end of the mail
> >>
> >>
05.04.2011 16:11, Florian Klaempfl wrote:
Yes, but but they need to be reviewed as well, no?
If they all were tested with delphi xe then no.
Best regards,
Paul Ishenin
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepasca
Am 05.04.2011 10:09, schrieb Paul Ishenin:
> 05.04.2011 14:26, Florian Klaempfl пишет:
>> Am 05.04.2011 04:27, schrieb Paul Ishenin:
>>> We probably can extend these tricks for other types and may be speedup
>>> the compiler.
>>>
>>> I think your branch should be reviewed either by Florian or by Jo
05.04.2011 14:26, Florian Klaempfl пишет:
Am 05.04.2011 04:27, schrieb Paul Ishenin:
We probably can extend these tricks for other types and may be speedup
the compiler.
I think your branch should be reviewed either by Florian or by Jonas
before the merge.
I can review the coding style etc. b
michael.vancann...@wisa.be wrote / napísal(a):
On Tue, 5 Apr 2011, LacaK wrote:
--or--
introduce any new method (ValidateFieldData ? ;-))) and let tdatsset
descendants use it:
{$IFDEF FPC}
ValidateFieldData(Field: TField; Buffer: Pointer);
{$ENDIF}
--or--
some smarter solution ?
The
On 04/05/2011 02:09 AM, Skybuck Flying wrote:
So in short what I am looking for is a pascal compiler which takes
care of all the work like "lexing/tokenizing/parsing/parse tree/syntax
tree/symantec checks/perhaps even optimizing the intermediate code"
and gives me something to work with like a
On Tue, 2011-04-05 at 08:11 +0200, Jonas Maebe wrote:
> On 02 Apr 2011, at 15:35, Joost van der Sluis wrote:
>
> > Done. Can someone who actually knows how to do that trigger a retry of a
> > testsuite-run, and a new testsuite-mail?
>
> Building still fails on darwin, I think because of a missing
On 5/4/2011 02:41, LacaK wrote:
Then please move approprate code at least into
TCustomBufDataset.SetFieldData
Thanks
This code was already there.
Should the 'Validate' code be moved there too ?
Yes. TDataset descendants are responsible to calling Validate, e.g.,
zeos call it inside TZA
On 04/05/2011 02:21 AM, Skybuck Flying wrote:
So it would be cool if free pascal compiler could compile pascal
sources into redcode assembly, which can then be further compiled by
the PMARS executable/assembler.
AFAIK, other than gcc, FP is designed to drop the ASM source code step
of code gen
On Tue, 5 Apr 2011, LacaK wrote:
--or--
introduce any new method (ValidateFieldData ? ;-))) and let tdatsset
descendants use it:
{$IFDEF FPC}
ValidateFieldData(Field: TField; Buffer: Pointer);
{$ENDIF}
--or--
some smarter solution ?
The whole code, which is repeated (and can be put in
--or--
introduce any new method (ValidateFieldData ? ;-))) and let tdatsset
descendants use it:
{$IFDEF FPC}
ValidateFieldData(Field: TField; Buffer: Pointer);
{$ENDIF}
--or--
some smarter solution ?
The whole code, which is repeated (and can be put in one place) is:
if not (State in [d
On Mon, 4 Apr 2011, Luiz Americo Pereira Camara wrote:
On 4/4/2011 10:28, michael.vancann...@wisa.be wrote:
On Mon, 4 Apr 2011, LacaK wrote:
Michael Van Canneyt wrote / napísal(a):
On Mon, 4 Apr 2011, LacaK wrote:
Then please move approprate code at least into
TCustomBufDataset.Set
33 matches
Mail list logo
