Announcement

Collapse
No announcement yet.

Why does the interface name conflict?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Why does the interface name conflict?

    I wonder why the name can conflict with existing interfacenames.

    I mean it's internally all guid-based right?
    hellobasic

  • #2
    Names must be unique because object variables must be declared using a name...

    LOCAL xxxobject AS IfaceName

    Comment


    • #3
      I can not use functionname Create in the interface.
      I know it's a constructor for the class but so far i don't know the interface will have a constructor..

      Though it does not compile.
      hellobasic

      Comment


      • #4
        From the help:
        They are defined at the class level, so they may never appear within an INTERFACE definition.

        Still i don't see a logic.
        If a constructor is not supported for interface (fine) why not support create as custom method?
        Maybe a future feature..?
        hellobasic

        Comment


        • #5
          Originally posted by Edwin Knoppert View Post
          From the help:
          They are defined at the class level, so they may never appear within an INTERFACE definition.

          Still i don't see a logic.
          If a constructor is not supported for interface (fine) why not support create as custom method?
          Maybe a future feature..?

          I'm missing something here. Why would you want to use CREATE/DESTROY within an interface?

          Stan
          Do not go quiet into that good night,
          ... Rage, rage against the dark.

          Comment


          • #6
            Because i just like the names??
            hellobasic

            Comment


            • #7
              Ok. Alles klar.
              Do not go quiet into that good night,
              ... Rage, rage against the dark.

              Comment

              Working...
              X