On Tue, 11 Nov 2008, Szak�ts Viktor wrote:
Hi Viktor,
>> I do not know the RL tool and it's internal format used
>> in .frm but for .mem files we can introduce new format
>> which will allow to store memvars with unlimited variable
>> name size.
> Of course, but how would you solve two way compat
Hi Przemek,
I do not know the RL tool and it's internal format used
in .frm but for .mem files we can introduce new format
which will allow to store memvars with unlimited variable
name size.
Of course, but how would you solve two way compatibility
for these .mem files?
I do not plan to imple
On Wed, 12 Nov 2008, Phil Barnett wrote:
Hi Phil,
> The difference is likely to be more pronounced when there are hundreds of
> variables that are public, vs hundreds of locals scattered throughout the
> software.
Neither in Clipper nor in [x]Harbour the speed of memvar variables
does not depe
On Tuesday 11 November 2008 05:01:15 am Przemyslaw Czerpak wrote:
> Have you checked it?
> You'll be very surprised if you will make some tests.
> In tests/speedtst.prg tests 1-15 checks the speed of
> local, static, public, privates and fields.
> Do you see noticeable speed difference between firs
-Messaggio Originale-
Da: "Szakáts Viktor" <[EMAIL PROTECTED]>
A: "Harbour Project Main Developer List."
Data invio: martedì 11 novembre 2008 11.43
Oggetto: Re: [Harbour] Clipper RL compilation problem
> I use them sometimes. LOCALs/STATICs don'
roject Main Developer List." <[EMAIL PROTECTED]
project.org>
Data invio: martedì 11 novembre 2008 10.06
Oggetto: Re: [Harbour] Clipper RL compilation problem
> Why? I agree that PRIVATE/PUBLIC should not be used at all but, >
pragmatically speaking, they are very powerful tools somet
Hi Przemek and all,
The point of this e-mail was to solve the RL problem
(with one possible way to solve it) and not debating
PUBLIC/PRIVATE matter in general or even considering
removing them and such, let's please focus on the point.
[ Unless there is any other obvious/existing solution
for t
-Messaggio Originale-
Da: "Szakáts Viktor" <[EMAIL PROTECTED]>
A: "Harbour Project Main Developer List."
Data invio: martedì 11 novembre 2008 10.06
Oggetto: Re: [Harbour] Clipper RL compilation problem
> Why? I agree that PRIVATE/PUBLIC
On Tue, 11 Nov 2008, Szak�ts Viktor wrote:
Hi Viktor,
> It's a Clipper '87 heritage and much slower than
> LOCAL/STATIC, it can make programs very difficult
Have you checked it?
You'll be very surprised if you will make some tests.
In tests/speedtst.prg tests 1-15 checks the speed of
local, stat
I had thought that we could limit PRIVATE/
PUBLIC var names to ten chars at runtime for
compatibility. PRIVATE/PUBLIC is not something
users want to use for new code,
Why? I agree that PRIVATE/PUBLIC should not be used at all but,
pragmatically speaking, they are very powerful tools sometimes.
-Messaggio Originale-
Da: "Szakáts Viktor" <[EMAIL PROTECTED]>
A: "Harbour Project Main Developer List."
Data invio: martedì 11 novembre 2008 3.31
Oggetto: [Harbour] Clipper RL compilation problem
I had thought that we could limit PRIVATE/
PUBLIC var nam
Hi all,
RL will crash when compiled with Harbour.
The problem is that it's using 10 chars longer
PRIVATE vars, then saves them to a .mem file
and restores them before doing anything.
Now, .mem files can only store var names up to
10 chars, so when the vars are restored their
names are truncated
12 matches
Mail list logo
