Hi!
I need something to play with! Where can I get an alpha version of CrossFPC?
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
Hi,
I don't know if it is FCP problem, it looks like it is, but I can't see how.
In XCode i've created a Carbon app with the given in main.c. When
running this, everything works as expected. However when I replace
Hello.app/Contents/MacOS/Hello with a version created by FPC from
hello.pp, I g
On Sun, 14 Aug 2005, Peter Vreman wrote:
> At 13:19 14-8-2005, you wrote:
> > Hi,
> >
> > attached is a patch from Juergen Rathlev which *should* fixes bug 4117 and
> > may fix 4234, too. It removes using of qword from fpreadpng.pp because
> > qword seems to be buggy and may probably improve th
On Sun, 14 Aug 2005, Dirk wrote:
> Hi,
>
> attached is a patch from Juergen Rathlev which *should* fixes bug 4117 and may
> fix 4234, too. It removes using of qword from fpreadpng.pp because qword seems
> to be buggy and may probably improve the performance of some functions, too,
> because it
At 13:19 14-8-2005, you wrote:
Hi,
attached is a patch from Juergen Rathlev which *should* fixes bug 4117 and
may fix 4234, too. It removes using of qword from fpreadpng.pp because
qword seems to be buggy and may probably improve the performance of some
functions, too, because it avoids redun
Hi,
attached is a patch from Juergen Rathlev which *should* fixes bug 4117
and may fix 4234, too. It removes using of qword from fpreadpng.pp
because qword seems to be buggy and may probably improve the performance
of some functions, too, because it avoids redundant shifting operations.
Dirk
At 07:33 8-8-2005, you wrote:
| > Okay, I researched the topic. Of course, yes, you can export functions
from an
executable
| > on linux. But freepascal doesn't seem to like it just yet.
|
| How do you intend to use the exported symbols of an stand-alone
| executable?
| As a shared library, or
At 10:46 3-8-2005, you wrote:
> I would suggest an "experimental" solution {$inline unsafe ?} which
does the
> inline without checks, and maybe gives a warning at compiletime: Warning:
> inlined func/proc might be unsafe.
The used registers still have to be known. For pascal code this is info t
