Is there any way of overloading the ^ (dereference) operator for a
user-defined type?
I'm looking at a simple Prolog interpreter written in TP3, i.e. 16-bit
code, and I think I might even have a fun use for it.
Obviously it's chock-full of segment:offset pointers but if ^ could be
overloaded
On Sat, 19 Sep 2009 10:25:20 +0200, Micha Nelissen wrote about Re:
[fpc-pascal] Re: getting started with threads:
> Graeme Geldenhuys wrote:
> > So far I have single interface for create/destroy/lock/unlock of
> > semaphores for Windows, Linux, *BSD. The latter two is actually for
> > all
>
> A s
2009/9/19 Micha Nelissen :
>
> A semaphore is not "locked" and "unlocked", it is posted and waited for.
True, and to let it make even more sense (technically correct) one
might have to use method names like deccount() / inccount() or
grabitem() / releaseitem() etc etc...
Either way, internal impl
On 19 Sep 2009, at 10:36, Micha Nelissen wrote:
Jonas Maebe wrote:
on x86 too). Atomic operations are not memory barriers by
themselves, and the fact that you perform an atomic operation does
not mean that afterwards all cpu's will immediately see this new
value.
Explain? Isn't the poin
Jonas Maebe wrote:
on x86 too). Atomic operations are not memory barriers by themselves,
and the fact that you perform an atomic operation does not mean that
afterwards all cpu's will immediately see this new value.
Explain? Isn't the point of an atomic update that it doesn't matter
whether t
Graeme Geldenhuys wrote:
So far I have single interface for create/destroy/lock/unlock of
semaphores for Windows, Linux, *BSD. The latter two is actually for all
A semaphore is not "locked" and "unlocked", it is posted and waited for.
Micha
___
fpc-p
Helmut Hartl pisze:
-Original message-
From: Dariusz Mazur
Sent: Fri 18-09-2009 16:24
To: FPC-Pascal users discussions ;
Subject: Re: [fpc-pascal] getting started with threads
David Emerson pisze:
I am getting started with threads (linux/cthreads) and I'm very happy so
far,
