> Maybe, but you can always build with mingw32 or visual C 6.0.
On Thu, 13 Jan 2005 15:07:28 +0100, Daan Leijen <daan@...> wrote:
>> Current Version developed on VC6, then CVS version doen't fix VC 7,1's
>> problem. (VC 7.1 supplied for VC7 user by Microsoft (without Academic
>> version user), so you don't care about VC7.)
> Uuh, I do not understand what you say here. However, you are right that
> I only use visual C 6.0 since I do not have visual C 7.0 -- I do care
> about it -- I have written parts of it :-) -- but I don't think it is
> currently worth the effort to see how it can work wxHaskell. One problem
> might be that you compile .NET code?
OK. I see.
I hesitated saying that you must use VC 7.1, Because current version
made by VC6, and I don't jugde the problems in wxc code or wxWidget code.
But you must (* notice *) that on wxHaskell website. Becase Microsoft
theSpoke Premium supply the VC7.1 low price for student, then perhaps
must use VC 7.1....and he see same problem.
I usally use VC 7.1, because I compile C++ hard template code, for example,
Boost library. But It has no relation with wxHaskell project.
If I bind hard template C++ code to wxc, I will negociate improve that
shelarcy <shelarcy capella.freemail.ne.jp>