Announcement

Collapse
No announcement yet.

Why does the interface name conflict?

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

  • StanHelton
    replied
    Ok. Alles klar.

    Leave a comment:


  • Edwin Knoppert
    replied
    Because i just like the names??

    Leave a comment:


  • StanHelton
    replied
    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

    Leave a comment:


  • Edwin Knoppert
    replied
    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..?

    Leave a comment:


  • Edwin Knoppert
    replied
    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.

    Leave a comment:


  • Tim Robbins
    replied
    Names must be unique because object variables must be declared using a name...

    LOCAL xxxobject AS IfaceName

    Leave a comment:


  • Edwin Knoppert
    started a topic Why does the interface name conflict?

    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?
Working...
X