Releasing WinHugs

[Krasimir Angelov]

The fptools Makefile system has htmlhelp target which builds both GHC
userguide and all library documentations for HTML Help. I hope that it
can be addopted for Hugs. I already have added HTML Help support for
Haddock.

Cheers,
  Krasimir

2005/9/7, Neil Mitchell <ndmitchell at gmail.com>:
> > If you don't count interact as a bug.  Do getChar/putChar work?
> putChar works fine, getChar doesn't. I can probably fix this up in the
> long run, I just don't have a clue where to start for now - the whole
> flow of control with the message pump, setjmp, polling etc. is quite
> confusing.
> 
> 
> > A WinHugs blurb for the User's Guide is important; it doesn't
> > have to be very long.
> That's easy enough. I'll submit something.
> 
> 
> > What would :main do?
> ":main arg1 arg2" would invoke main, but getArgs would return
> ["arg1","arg2"] for that execution. This would be fantastically useful
> for testing console programs. This would be a Hugs improvement, not
> specific to WinHugs.
> 
> 
> > You might like to check whether HGL works with WinHugs: try running
> > main in hugsdir/demos/HGL/GTest.hs -- it should pop up lots of windows
> > that react to events in different ways (README in that directory gives
> > the details).
> 
> First off, it doesn't load. By changing the path from
> {Hugs}\packages\*
> to:
> {Hugs}\packages\HGL;{Hugs}\packages\Win32;
> 
> I get it to load. Is this a Windows problem, or a more general problem?
> 
> Once I get it running, typing main brings up all the windows.
> Unfortunately playing with them gives warnings like:
> 
> Run-Time Check Failure #0 - The value of ESP was not properly saved
> across a function call.  This is usually a result of calling a
> function declared with one calling convention with a function pointer
> declared with a different calling convention.
> 
> inside incMallocPtrRefCnt
> 
> And every so often it crashes.
> 
> 
> > - Need to check whether the Unicode stuff works under Windows.
> I doubt it, but fundamentally the controls are all operating system
> controls, and should support unicode. Its just a case of replacing
> char* and CHAR* for LPTSTR, then checking.
> 
> > - The plain interpreter hasn't been built under VC++ for some time;
> >   someone needs to do that and test it.
> I did it when I submitted the project files for msc, its fine for
> basic use, I didn't extensively test it.
> 
> > - WinHugs builds under MSYS+MinGW, but the executable just hangs.
> >   (Not essential to fix this, but would be nice.)
> I will install the required MSYS+MinGW and see what happens, I
> wouldn't have expected it to hang, but it should be fixable.
> 
> > - Someone will have to do the Windows packaging, including the program
> >   compiled with VC++ (for the stack overflow protection) and the
> >   documentation is HTML Help form.
> I don't know how to compile the HTML Help, but I'm sure I can figure
> it out. I have builds of the 3 binaries for Hugs.
> 
> Thanks
> 
> Neil
> _______________________________________________
> Cvs-hugs mailing list
> Cvs-hugs at haskell.org
> http://www.haskell.org/mailman/listinfo/cvs-hugs
>