| > 3) More important... Where is winhugs? | | After any release, it takes a few days or so to get all the various | sub packages on the web page. Though Winhugs is a nice package, it | has to be compiles under a specific compiler, (Borland, I think) | so it always takes a few days for the build of Winhugs to get built | after the main release. As I understand it, the current Hugs maintainers don't have access to the Borland compiler (version 4.52) that is used to build winhugs. I'm not on the Hugs team any more, but I do have a copy of the compiler, and so I've made up a winhugs binary from the Feb 2000 Hugs 98 sources, which you can download from: http://www.cse.ogi.edu/~mpj/Feb2000winhugsUNSUPPORTED.zip If Andy decides to put a copy on the main Hugs pages, then I'll remove this copy within a few days. As the name suggests, I'm not offering to provide any support for this, so please test it thoroughly before you do anything that relies on it. Despite some significant performance problems, and also some incompatibilities with certain (Win32-oriented) Hugs programs, some folks still prefer this version over the plain console version of Hugs. But it has always been difficult for the Hugs maintainers to support winhugs, and so it's entirely possible that there will not be any further releases of winhugs. Jose Gallardo, who wrote the original Windows interface around which winhugs is built, has, I believe, produced a new version of winhugs that avoids may of the problems of this version. There was a plan to make his new version available from the Hugs web pages, but perhaps that has fallen through. Alternatively, I might mention that Borland have now made a more recent version of their compiler available to download from the web; perhaps some of the more adventurous winhugs users out there might grab a copy of that and use it to compile, maintain, and perhaps even distribute future versions of winhugs. All the best, Mark
