How should i implement a delegate in VB6?

I need to implement delegates in VB6, having some experience in C# and read
about AddressOf in VB6 but am not sure how to call the procedure at the
address.

The application should evaluate the state of certain variables and call a
corresponding method, the operators of the expression being evaluated and
the resulting method to be called should be configurable without touching
the code. Have read about CallByName, but need a solution that's as fast as
possible because app will be talking to a PLC



.

Relevant Pages

  • Re: How should i implement a delegate in VB6?
    ... Joris van Lier wrote: ... about AddressOf in VB6 but am not sure how to call the procedure at the address. ... but need a solution that's as fast as possible because app will be talking to a PLC ...
    (microsoft.public.vb.syntax)
  • Re: Microsoft doesnt want you to use VB .Net
    ... If you know OO, then vb.net should be a huge relief, easier to code than vb6 ... Delegates are so hard to learn, ... >> I had to transition and have others also transition, ... >> business, but can you give an exampleof something thats not being ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Delegates are useful, and here is why (sample program)
    ... just a programming paradigm. ... Delegates are just function pointers closed over the first argument of ... Events are just syntactic sugar for the Observer ... with VB6, either: VB6 had events which were vaguely similar ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Translate VC (delegate) to VB6
    ... in fact it was about delegates, but with a totally different sample: ... I have no real idea how to convert this to VB6, in fact it is even unclear to me what this line does. ... It's from an old software that we bought and which we would like to re-release. ...
    (microsoft.public.vb.com)
  • Re: Syntax Difference C#/VB.NET when calling a Method
    ... The ambiguity existed in VB6 with default properties but there is nothing ambiguous about the syntax in VB.NET - it's just different. ... The less common behavior (passing a function pointer) requires an additional keyword ... I personally like this (although I find *addressof* a little too "implementation-oriented" as a keyword - after all if you pass an object to a function you're also passing it's address. ...
    (microsoft.public.dotnet.framework)