Makes perfect sense, thanks for the quick answer :-)
Florian Klaempfl wrote:
Ror/rol are very sensitive against data type changes so this ensures you
get always the desired result. While x shr 1 has the same result if the
value fits in x, ror(x,1) has different results if x is a byte, word or
dw
Quick question: Is there any particular reason why the system function
ror() (in /fpc/rtl/inc/systemh.inc) has been divided up into rorbyte,
rordword and rorqword (and respectively for rol() ) instead of being
overloaded?
___
fpc-pascal maillist - f
Thanks Jonas.
I could have sworn I had it installed and never bothered to check. Shows
that one should never assume ;-)
But it's good to you explained this linker behaviour though, for future
reference.
-- MG
___
fpc-pascal maillist - fpc-pascal
Hi All!
I've noticed that someone made a headstart with a unit to bind with FUSE
in FreePascal at http://bugs.freepascal.org/view.php?id=12218. I've
taken the last two entries (FUSE-2008-12-20-3.PP and
Test-2008-12-20-3.PP) and modified the test file on line 88 to use the
move() function inst
I can see x86_64-freebsd in the FPC make file, so you ought to be able
to build it with the source. Just add the parameters OS_TARGET=freebsd
and CPU_TARGET=x86_64
-- Mike
Francisco Reyes wrote:
Are there any plans for a FreeBSD AMD64 version?
Sometime ago I tried to work on this and since I
Hello Hansi,
I am using Synapse for all my socket work, so this might be a bit
different for you. But for a blocking listener in a thread (waiting at
an Accept), I call AbortSocket. It immediately stops all work on the
socket and lets you do the things you need to do. I'm sure there's a
simil
Hello everyone!
I just happened to see the license on fina.inc / finah.inc and a few
other includes by Gertjan Schouten, which are used in SysUtils
(/rtl/objpas/sysutils). They're released under the GNU GPL, but don't
mention anything about the special exception/persmission (COPYING.FPC).
So
Hi Danie,
Other than what was pointed out with create/destroy, wouldn't it create
a memory leak with the NEW?
procedure TForm1.Button1Click(Sender: TObject);
begin
if pTopCV = nil
then begin
NEW( pTopCV );
pTopCV^ := TControlVolume.Create(PanelDraft);
Instead, simply do
Hi John!
I saw someone else that posted a similar issue. Are you using Vista? If
so, this might help:
* **Right-click** (not the usual left-click) the FPC folder from My
Computer and select "Options" from the drop-down list (bottom entry).
* There are 4 tabs at the top of the new window, on
