Re: "scrrun.dll" not compatible in different languages?



"J French" <erewhon@xxxxxxxxxx> wrote in message
news:42c8d3bb.230482288@xxxxxxxxxxxxxxxxxxxxxxx
>
> On Sun, 03 Jul 2005 15:45:40 GMT, "Michael D. Ober"
> <obermd.@.alum.mit.edu.nospam> wrote:
>
> >
> >That's a lot of code for something that should be built into the
language.
> >C++ correctly handles the three most common end of line markers natively.
> >The fact that VB 6 doesn't without the assistance of an external
component
> >is simply a flaw in the language. I'll stick with FSO or move to VB 2005
> >(the beta handles this correctly) when it's released. Obviously,
existing,
> >working code won't be ported as there's no benefit from doing so.
>
> You'll find that the Class I posted is bi-functional
> - it supports delineated file reading and block input
>
> Note also that the delineator is under the programmer's control, it
> could be anything.
>
> C++ is just a load of libraries, any special behaviour has been
> written by a programmer.

Libraries that are part of the ANSI standard. As for special behavior,
_ALL_ special behavior in a program is written by a programmer.

>
> I suppose you know that the FSO will simply not work on well set up
> machines, since it is part of VB Scripting (AKA Viruse Gateway) canny
> administrators disable it.

Some do, some, such as myself, use other methods to block viruii. I haven't
had a virus get lose on my network in over 4 years and I have VB Scripting
turned on - it's simply a matter of have a good virus scanner that's updated
daily (not weekly as most AV companies do) along with appropriate network
security policies in place.

>
> However, since you seem to have some peculiar ideas about what should
> and what should not be supplied by a language,

Actually, this group has helped me on numerous occassions and I have also
provided assistance here. The fact that VB 6 doesn't support multi-platform
file IO is a flaw (and shows that VB's roots are in DOS)

> I suggest that you
> migrate to VB.NET
> - we obviously cannot help you here

This and other VB newsgroups have been useful over the years, much more so
than TechNet. I have also posted solutions here.

I will be once VB 2005 is released. After using BETA 2 for some projects, I
find the .NET class library to be extremely helpful. However, I have no
plans to migrate existing code as there is no real up-translator for VB 6 to
VB 2005. VB 6 is procedural with object support while VB 2005 is object
oriented with procedural support. This fundamental difference makes it
nearly impossible to write a good language translator. The provided
translator is useful for short segments of code however, which eases the
transition process.

Mike Ober.



.