Rick, I'll compile later today with VC++ 6 and get the exact compiler messages. They were errors preventing compilation, but I don't recall the exact wording.
When I get that we can talk it over, maybe there is another solution for VC++ 6. If not, then so be it. I already know I'm not in favor of going through a bunch of contortions just to get the code to compile under a compiler version that is 10 years out of date. It's nice if we can do it, but it is really only a convenience for people that have VC++ 6 installed. The free Visual C++ express versions of the compilers work fine with the code base. So there is nothing to prevent anyone that wants to work with the source code on Windows from doing so. -- Mark Miesfeld On Fri, Oct 3, 2008 at 5:55 AM, Rick McGuire <[EMAIL PROTECTED]> wrote: > I have a similar concern about memory leaks. For a delete operation, > the type of the object being deleted is important to ensure that the > correct delete operator is getting called. I'm not sure what happens > when that pointer is cast to a void *, but I'd rather have the correct > thing happening on all platforms rather than keep this in just for > VC++ 6. Since we don't use that compiler version for the production > builds, supporting that compiler version is not of the highest > priority (I think). I'm interested in hearing Mark's opinion on this > though, since he's closest to the issue. > > Rick > > On Fri, Oct 3, 2008 at 8:49 AM, Moritz Hoffmann <[EMAIL PROTECTED]> wrote: >> Rick McGuire wrote: >>> Mark, >>> >>> This change backs off some changes you make to supposedly allow the >>> code to compile on VC++ 6. The original version was the correct one, >>> but I was ok with this change as long as it didn't cause problems >>> elsewhere. It is appears it does. I suspect this means we can't >>> support VC++ 6 any more. >> >> Well, I don't know what happens besides the warning in GCC, but it >> complained about not being able to delete void pointers. If I interpret >> this correclty this means that the memory can not be freed, leading to a >> leak. However, if my assumption is false I could live with the warning >> if it is required for VC++ 6. >> >> Now I remember the discussion a wile ago about VC++ 6... >> >> Moritz >> >> >> -- >> Moritz Hoffmann >> http://antiguru.de/ >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
