D3 Optimise and REMOVE

#21

On Jul 25, 2:31*pm, Excalibur21 <pgmcmur... (AT) gmail (DOT) com> wrote:

Quote:

Hi Ross
Which of the 10,000 varieties of Unix do you use? *

Bog standard Centos 5.5 - You could opt for Red Had if you wanted to
pay for support, but you would get all you are likely to need with
little issue from your friends @ Google

Quote:

Yes Linux is just
another variety, so Linus did a base module a bit like DOS really and
the other 96% is everyone and his dog's idea of what should happen.

Actually, companies like Red Hat decide what they are going to put
into a "distribution", but just as with Windows, you are fre to buy or
install free software over the base OS to your hearts content

Quote:

Problems - Zero support as there are so many versions and most support
shops do Windows as that is what 95% of office users have. *

We find that our Linux based systems require zero support, which was
(and is) not the case with Windows in general in our experience.

Quote:

The reason Unix/Linux
based organisations have to spend a poultice on in house support.

Not the case in the "real world" that we operate in

Quote:

In D3 Linux one is stuck with the VME whereas the Windows FSI is
great.

Once more, our experinces differ. If TL ever introduced FSI to D3/
Linux that would be the day I started moving to alternatives in
earnest. Basic features like "within" don't work in the FSI, nor does
all indexing (try loading/using the D3 REF account from thye FSI) ....
One mans "stuck" is anothers "blessed"

Quote:

A pity about the optimise issue. *I gather from TL that they are now
preferring the word Flashed to optimise although it is the latter in
the documentation for Compile. *

AFAIK it has ALWAYS been called "Flash compiled" or "flashed" -
"optimization" was simply a "feature" of early flashed code when it
produced REAL C modules that were compiled through a C compiler -->
the gain didn't justify the pain, so multiple optimization levels are
a relic from the past and simply don't exist (within the context of
"flash compilation")

Quote:

I suspect that the problem lay hidden
for so long because so many avoided it. *However the small stand alone
routines favoured with MVSP etc really do mean flashing has a
significant benefit. *

Flash compiled code has ALWAYS yielded a significant benefit,
especially in areas like string manipulation, regardless of the size
of the code

Quote:

nb all it has not been NT for many moons.

Actually, it was only with v9 in September last year that the name
changed to D3/Windows - 7.5 still referred to it as D3/NT ..... but
the name change was LOOOOOONG overdue!

Quote:

We wasted a small fortune on Unix through the '90s I really do not
want that pain again. *

Funny, we did the same on D3/NT (worse than early releases of
"Advanced Pick Native" :-)

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

D3 Optimise and REMOVE

comp.databases.pick comp.databases.pick

Re: D3 Optimise and REMOVE - 07-26-2011 , 12:49 AM