On 2/3/06, k. holwerda <[EMAIL PROTECTED]> wrote:
> John Labenski wrote:
>
> >are in wxLua as just "wx.enum1". I propose that it be changed to
> >"wx.MyClass_enum1" where we throw away the enum name, but keep the
> >class name. This way we unclutter the global wx namespace with
> >seemingly arbitrary enum values which should logically tie them more
> >closely to the class that they actually belong to and are used with. I
> >think that to go as far as calling the enums
> >"wx.MyClass_SomeEnumType_enum1" is probably too much and I don't think
> >we'll run into to problems by not bothering to implement that since
> >C/C++ doesn't enforce you to use the enum name anyway.
> >
> >Anyone have any concerns about this change?
> >
> Even in C++ one gets the enum value with
>
> MyClass::enum1
>
> like e.g. :
>
> a2dFill* clone = m_fill->TClone( MyClass::enum1 );
>
> That is without the SomeEnumType in it..
> So why not do:
>
> wx.MyClass.enum1
>
> or
>
> wx.MyClass:enum1
>
> I don't understand the _ there. Of is it impossible to do it like that??
Because we'd have to make a table of the enum values for each class
name requiring far more complicated code. I thought that just using an
underscore would be a happy medium.
Regards,
John Labenski
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Wxlua-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wxlua-users
