- Cvs-hugs - Haskell.org

cvs commit: hugs98/src input.c
by Ross Paterson 01 Sep '05

01 Sep '05

ross 2005/09/01 07:49:24 PDT Modified files: src input.c Log: from Neil Mitchell: When saving stuff before auto-reloading files, it is no longer necessary to save the input buffer in Windows - the standard control takes care of this automatically. Revision Changes Path 1.87 +2 -8 hugs98/src/input.c

1 0

Patch for input.c
by Neil Mitchell 01 Sep '05

01 Sep '05

Hi, When saving stuff before auto-reloading files, it is no longer necessary to save the input buffer in Windows - the standard control takes care of this automatically. Thanks Neil

1 0

cvs commit: hugs98/src errors.h
by Ross Paterson 01 Sep '05

01 Sep '05

ross 2005/09/01 07:35:34 PDT Modified files: src errors.h Log: whitespace Revision Changes Path 1.12 +5 -5 hugs98/src/errors.h

1 0

Patches for error.h and error.c
by Neil Mitchell 01 Sep '05

01 Sep '05

Hi, Attached is a patch for error.h/.c. Some comments: The WinHugs specific bit now uses int instead of INT, so its not dependant on windows.h The error message on compile time errors now puts out a hyperlink, this is #if'd so shouldn't change non WinHugs. This allows WinHugs users to click when an error occurs and be brought to that location in their editor. Instead of proding MessageBox(hWnd), I have defined InfoBox and ErrorBox which WinHugs does something sensible with. The header file uses cleaner interaction with WinHugs, instead of poking the magic hWnd.. Thanks Neil

1 0

cvs commit: hugs98/src/winhugs menusbm.c winhugs.rc
by Ross Paterson 01 Sep '05

01 Sep '05

ross 2005/09/01 05:42:00 PDT Modified files: src/winhugs menusbm.c winhugs.rc Log: missing bits from last commit Revision Changes Path 1.3 +4 -4 hugs98/src/winhugs/menusbm.c 1.13 +328 -216 hugs98/src/winhugs/winhugs.rc

1 0

cvs commit: hugs98/src/winhugs DlgAbout.c DlgMain.c DlgOptions.c General.c Header.h History.c IORemap.c IORemap.h Legacy.c MruFiles.c Registry.c Registry.h RtfWindow.c RtfWindow.h ScriptMan.c StartCode.c Winbrows.c Winframe.c Winframe.h Winhint.c ...
by Ross Paterson 01 Sep '05

01 Sep '05

ross 2005/09/01 05:22:19 PDT Modified files: src/winhugs/resource hugs1.ico hugsdoc.ico logo.bmp Added files: src/winhugs DlgAbout.c DlgMain.c DlgOptions.c General.c Header.h History.c IORemap.c IORemap.h Legacy.c MruFiles.c Registry.c Registry.h RtfWindow.c RtfWindow.h ScriptMan.c StartCode.c resrc1.h src/winhugs/resource rt_manif.bin toolbar.bmp winhugs.manifest Removed files: src/winhugs Winbrows.c Winframe.c Winframe.h Winhint.c Winhint.h Winhugs.h Wintext.c Wintext.h Wintoolb.c Wintoolb.h Winutils.c Winutils.h config.bat winhugs.c Log: New WinHugs implementation, from Neil Mitchell, reformatted in house style. Changes in .. to make it work are on the way. Revision Changes Path 1.2 +14 -1 hugs98/src/winhugs/resource/hugs1.ico 1.2 +1 -1 hugs98/src/winhugs/resource/hugsdoc.ico 1.2 +1 -1 hugs98/src/winhugs/resource/logo.bmp

1 0

WinHugs progress report
by Neil Mitchell 01 Sep '05

01 Sep '05

Hi, I've been working on rewriting WinHugs recently, to make it work and to make it more Windows compliant. I have put a screenshot up at http://www-users.cs.york.ac.uk/~ndm/projects/winhugs.php, and my todo list is http://www.haskell.org/hawiki/NeilMitchell/HugsNotes which includes the bugs I'm working on, and a list of the good and bad points about the rewrite. I have a version which I am now using as my primary development environment. Its stable and reliable. Out of the bugs mentioned in the Todo list only the options dialog not giving people -/+98 and other super-haskell options is real enough to stop people using it, if they want non-standard haskell. All the others are very minor. While I'm rewriting it I've tried to reduce the amount Hugs knows about WinHugs. For example, I've removed #include <windows.h> from prelude.h. There are quite a few changes to the hugs files, 8 files have been modified, none that substantially. All the changes are pretty local, and in general seem to be positive ones, I think. The changes in the WinHugs directory are pretty much total, its almost unrecognisable. There are 4 chunks of code that have survived, and those have all been marked with big warnings. Most of the files have changed name, there are a lot more smaller and self contained modules. It's not the same at all. Once the first modifications are made to the hugs directory, the existing winhugs code will be dead forever, the two code bases are sufficiently different that its unlikely to be able to run them side by side off the same hugs code, without some effort (not too much, but I can't imagine anyone will want to do it). With this in mind, how would be best to go about merging in WinHugs2? 1) Delete WinHugs and start from scratch. 2) Make a WinHugs2 directory, and keep WinHugs around for the past, accepting it probably won't build. 3) Find someone who wants to resurect the dead WinHugs1... (maybe) And also when does WinHugs2 integration want to take place? Thanks Neil

2 4

Updated hugs msc projects
by Neil Mitchell 31 Aug '05

31 Aug '05

Hi, Attached are the updated project files for hugs and runhugs, the console versions, with the required files to build on windows. They are in the VS.NET format, the existing ones are broken (not badly, just slightly) and in VS6 format. These can happily coexist with the old ones. With these project files, the latest version of hugs builds from CVS on Windows with Visual Studio .NET happily, without any patches. Please place these files in src/msc Thanks Neil

2 2

Hugs for Windows icons
by Neil Mitchell 31 Aug '05

31 Aug '05

Hi, I have updated the icons in the "icons" directory. In the past these were a 32x32 icon which is scaled by the OS for 16x16 and 48x48 sizes, which doesn't look very good at all. The attached icons are all natively in all 3 sizes. In addition, they use anti-aliasing on the lambda to make it fit in better with the rest of the computer. They are still 16 color, using the standard windows 16 color palette, so should work perfectly on older computers as well. I have uploaded a .png of all the icons, see http://www-users.cs.york.ac.uk/~ndm/projects/winhugs.php at the bottom. The first 3 are attached to this email (in order: hsicon, hugsicon, hsxicon), the bottom row are the new WinHugs icons, which aren't attached. Thanks Neil

1 0

WinHugs, Haskell bug
by Neil Mitchell 31 Aug '05

31 Aug '05

Hi, The following code > let x = 1 in x Gives the following error on WinHugs, the latest development build (my private one) > ERROR - Syntax error in expression (unexpected keyword "in") When run in either a very old copy of WinHugs, or GHCi I get > 1 I think this has been occuring ever since I started development, quite possibly before, as a few early bugs were caused by this - long before I was tracking bugs. Does the vanilla CVS version accept this? I haven't changed much (as far as I can tell, none) parsing/execution code. Thanks Neil

1 1