Re: wxEuphoria v0.15.0

new topic     » goto parent     » topic index » view thread      » older message » newer message
mattlewis said...

I've stayed with 2.8 so far mainly because that's what wxWidgets considers stable (though they believe that 2.9 is pretty robust).

wxWidget site says: “2.9 series bring many improvements compared to 2.8 series and, in spite of being called a development release, we believe that 2.9.1 can be used in production environment, especially for the new projects for which (small) changes in behaviour since 2.8 are not a problem.”

mattlewis said...

Also, yes, time is definitely a factor.

That’s understandabl;e.

mattlewis said...

I'd recommend first looking at the wxEuphoria Developers section The wrapper functions in C++ are pretty straight forward, for the most part, and there are lots of examples from which to base new stuff.

I will have a look. For a long time, for me, a complex Assembler program looked exceedingly simple, and conversely, a simple C or C++ was a big challenge to me.

mattlewis said...

Getting 2.9 up and running will take a bit more work. I think they made some changes to the way wxStrings work,

wxWidgets site says pf 2.9 “(small) changes in behaviour since 2.8” I do not buy that argument. It is also completely Unicode so even your English language Ascii page would have to be brought up to 2 bytes level like Microsoft’s internals. We can have debate whether or not to go UTF-8 route (your preference for Linus would tend to drag you that way), but as of now, there is no problem with memory availability, and since Euphoria is already at 4 bytes per character level, one might stick to a 32 bit (or rather 21 bit) level . Welcome, Chinese audience!
C, C++ and assembler routines to convert are already available and debugged, and would, in any case, be easy to develop in Eu. At a personal level, I have a problem with variable number of two bytes per Indic word. Simply put, the complexity (variable number of bytes) is exactly same as with UTF-8 to ANSI and vice versa. I am in the process of solving my problem using location E000 private pages of Unicode.

mattlewis said...

Another thing I've been wanting to do is to start using MinGW builds for Windows. I haven't been able to build anything with Watcom since 2.8.7.

I think I have somewhere in my hardware, a cheat sheet of conversion of C level string functions to bring it all to Microsoft’s two byte per character. It is a major overhaul of Euphoria to get it to that level and then you would use MinGW or Visual C++ easily. However, since Euphoria does not really have a string type, it might be fairly easy.
I have toyed with the idea of doing it but my mental block against C++ stops me from going ahead.

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu