Catching up (my apologies)

Robert (and everyone else),

Sorry, I assumed that since I created this list that I was subscribed to 
it as well. I wasn't. Oops. Let me try and catch up with your past emails.

Daan suggested we take a look at the C library used by the Eiffel 
binding. Bryan has done some work to automate our C code generation, but 
reuse is good, and we should check it out. I will try to have a look and 
see how much effort it would take to convert our existing code.

Robert had a bunch of posts...


Re: using the wxWindows naming conventions.

I think this is a good idea. We can always add a ".net-ified" version in 
addition to the standard calls to make everyone happy. For the macros 
like EVT_MENU(...) we could do:

   class EventListener
   {
      public void EVT_MENU(int id, EventListener func) { ... }
   }

This could just call AddEventListener() (or it's renamed replacement) 
internally, which is how wxWindows works anyway. Bryan has said that he 
will look into this. I thought converting to a more C# like naming 
convention was good at the time, but in hindsight it doesn't appear to 
be working out very well.


Re: Linker errors

I have not seen this problem. Are you still having it? If so, let me 
know and I will help investigate.


Jason
379




-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en