Marc Weustink wrote:
Copy back was already thrown away with Fortran 66 I think because it
caused too much trouble.
I'll believe it will give troubles in certain situations, I only have no
idea where (then again, I'm only a compiler user).
r.i could have also an alias so the example above isn't
At 20:02 16-10-2004, Florian Klaempfl wrote:
Marc Weustink wrote:
At 00:15 14-10-2004, Florian Klaempfl wrote:
Marc Weustink wrote:
At 16:38 13-10-2004, Jonas Maebe wrote:
On 12 okt 2004, at 22:12, Marc Weustink wrote:
M:> Is a sigbus catchable so that you can read the data and continue
as if noth
Olle Raab wrote:
04-10-16 19.40, skrev Chess Player följande:
If packed records are such a problem, don't use packed records. We're not
programming for computers with 640kb of RAM.
"packed" is sometime used to make the binary representation of the record
more predictable, which you might need if
04-10-16 19.40, skrev Chess Player följande:
> If packed records are such a problem, don't use packed records. We're not
> programming for computers with 640kb of RAM.
"packed" is sometime used to make the binary representation of the record
more predictable, which you might need if you mix fpc
Marc Weustink wrote:
At 00:15 14-10-2004, Florian Klaempfl wrote:
Marc Weustink wrote:
At 16:38 13-10-2004, Jonas Maebe wrote:
On 12 okt 2004, at 22:12, Marc Weustink wrote:
M:> Is a sigbus catchable so that you can read the data and
continue as if nothing happened (or is that something at OS leve
If packed records are such a problem, don't use packed records. We're not
programming for computers with 640kb of RAM.
__
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
___
On 16 Oct 2004, at 18:41, Olle Raab wrote:
Some time ago Florian did mention to add emulation of 80-bit Extended
typ,
to make it possible to create e. g. powerpc-intel-cross-compilers...
It was needed because Extended constant expressions is to be evaluated
during compile time.
Actually, I though
04-10-13 16.38, skrev Jonas Maebe följande:
> We also don't emulate the 80-bit
> extended type on processors which only have a 64-bit double precision
> fpu. We also don't emulate endianess. Portability has a lot of
> pitfalls.
Some time ago Florian did mention to add emulation of 80-bit Extended
On 13 Oct 2004, at 23:02, Marc Weustink wrote:
We also don't emulate endianess. Portability has a lot of pitfalls.
In a matter of fact, you do support endianness. As an enduser I don't
have to take care ot the phisical representation of an integer for
instance.
An integer and $FF is still a value
At 00:15 14-10-2004, Florian Klaempfl wrote:
Marc Weustink wrote:
At 16:38 13-10-2004, Jonas Maebe wrote:
On 12 okt 2004, at 22:12, Marc Weustink wrote:
M:> Is a sigbus catchable so that you can read the data and continue as
if nothing happened (or is that something at OS level)
That is normally
Marc Weustink wrote:
At 16:38 13-10-2004, Jonas Maebe wrote:
On 12 okt 2004, at 22:12, Marc Weustink wrote:
M:> Is a sigbus catchable so that you can read the data and continue
as if nothing happened (or is that something at OS level)
That is normally possible, yes. But as Florian said, it's quit
At 16:38 13-10-2004, Jonas Maebe wrote:
On 12 okt 2004, at 22:12, Marc Weustink wrote:
M:> Is a sigbus catchable so that you can read the data and continue as
if nothing happened (or is that something at OS level)
That is normally possible, yes. But as Florian said, it's quite a bit of
work and a
Jonas Maebe wrote:
M:> But how are members of packed records accessed ?
Just like members of regular records. The difference is that there are
simply no alignment bytes between the different fields of the record.
If you've to access an unaligned member, you've to use a move as you do
in C, whe
On 12 okt 2004, at 22:12, Marc Weustink wrote:
M:> Is a sigbus catchable so that you can read the data and continue
as if nothing happened (or is that something at OS level)
That is normally possible, yes. But as Florian said, it's quite a bit
of work and also extremely slow (you get 4 context sw
Hi,
Florian and I had a discussion on IRC and we decided to continue it here.
F:> I guess the main problem will be that the typeinfo structures has
changed to fit sparc 's alignment
M:> this will be on sparc only ?
F:> on cpus which define FPC_REQUIRES_PROPER_ALIGNMENT
F:> mainly, the data after s
15 matches
Mail list logo
