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

On Tue, 05 Jul 2005 12:06:50 GMT, "Michael D. Ober"
<obermd.@.alum.mit.edu.nospam> wrote:

<snip>

>> 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.

Eh ?

>> 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.

Yes, well your programs may well not work under other regimes

>> 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)

It shows nothing of the sort
- VB's roots go back well before DOS
- CP/M - Apple - Commodore - all had versions of BASIC from M$

>> 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.

It would be very funny if it did not have 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.

Go back and look at the OP's original post

He was getting grief from using the FSO
- your reply was that VB is rubbish because it's Line Input does not
support #10 delineated text files.


.

Relevant Pages

  • Re: [LONG] Re: Why code completion and early error checking are needed
    ... >> the programmer who wants such features. ... > libraries to find the type declaration. ... If you type std::vector that means the one from the Standard. ... > of the language to have certain naming and declaration standards ...
    (comp.lang.cpp)
  • [LONG] Re: Why code completion and early error checking are needed
    ... > the programmer who wants such features. ... the guiding principles in the evolution of the c++ language should be ... the problem with this is that ide must first be able to assume ... libraries to find the type declaration. ...
    (comp.lang.cpp)
  • Re: Odd behaviur...
    ... libraries, most of which are your own, the includes are easily managed. ... >>left wondering why a programmer capable of producing such code would ... Delphi and inserted as dlls into the existing C code base. ... made to new looking apps with Delphi GUI and C dlls carrying the older code. ...
    (comp.lang.pascal.delphi.misc)
  • Re: Oft-shared (perhaps?) Impressions of a Lisp Newbie
    ... library" of Common Lisp? ... If something isn't in the language, it will be in some common library, ... you might find M linked list libraries and N ... The more years you spend as a programmer, the more you learn ways to ...
    (comp.lang.lisp)
  • Re: The Lib debate
    ... I am not against code-reusing technics. ... there is not real programmer that to write everything from scratch ... BUT, like everything in this world, code-reusing and libraries ... and technics that are for fully assembler written applications. ...
    (alt.lang.asm)