On 2 mrt 2005, at 07:29, Florian Klaempfl wrote:
- FPC's random is probably more complex
Indeed. I guess Delphi's is still a simple "(x * prime1) mod prime2" or
so. FPC uses the Mersenne twister.
Jonas
___
fpc-pascal maillist - fpc-pascal@lists.freepa
On Wed, 2 Mar 2005 11:05:50 +0100, Jonas Maebe <[EMAIL PROTECTED]> wrote:
>
> On 2 mrt 2005, at 07:29, Florian Klaempfl wrote:
>
> > - FPC's random is probably more complex
>
> Indeed. I guess Delphi's is still a simple "(x * prime1) mod prime2" or
> so. FPC uses the Mersenne twister.
>
> Jonas
Hi,
I'm using several defines like this:
{$define M1}
{ $define M2}
{ $define M3}
{ $define M4}
...
Any time I have to change them, I have to touch all one by one, because
they're mutually exclusive.
Is there method of saying: {$undef M1..M15}?
Or a better basic approach?
TIA,
Marc
___
> I'm using several defines like this:
>
> {$define M1}
> { $define M2}
> { $define M3}
> { $define M4}
>
> Any time I have to change them, I have to touch all one by one, because
> they're mutually exclusive.
>
> Or a better basic approach?
Maybe I am missing something, but why not just have
Am Do, den 03.03.2005 schrieb Jeff Miller um 13:56:
> > I'm using several defines like this:
> >
> > {$define M1}
> > { $define M2}
> > { $define M3}
> > { $define M4}
> >
> > Any time I have to change them, I have to touch all one by one, because
> > they're mutually exclusive.
> >
> > Or a bet
> unit b;
> ...
> {$undef M1-M15}
Such constructs won't work, for the same reason that variablenames with
numbers in it can't be used as such.
For the compiler it is an alphanumerical identifier, and the number(s) have
no meaning.
___
fpc-pascal mailli
