Re: Standardisation between Win libraries
- Posted by Pete Lomax <petelomax at blueyonder.co.uk> Jul 25, 2003
- 560 views
----=_6es0iv83csi4qi5h6ad975116go7iip3v1.MFSBCHJLHS I'd just like to remind everyone that Jacques Deschenes posted a file back in 1999 containing nearly 6000 constants; I have a copy of lcc which comes with 325+ header files, many of which are trivial, but one of which I know contains 16,600+ lines (not all constants, but the point is made). In contrast, my own ppconst.e contains just the constants my program needs (and a fair few it don't), is only 341 lines long (including some from get.e, database.e, etc). And my program is far from being trivial !! (Watch this space). I would like to see a w32const.ew file, for searching purposes, but: a) it would be up to Derek to create that if he chooses, and he/win32lib would gain little to nothing from doing so. b) it is obviously up to Arwen/WinMania/Llama/etc to use that, if they so chose, and they may well not, same deal. c) some mechanism would need to be in place that any mod to said file does not crash any other install. Fundamentally, that is not possible. SUMMARY =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D I ain't gona happen. It is easy to create your own mini-lib for the things you need. I've attached mine, if someone wants to make this their pet project (proving it works with everything mentioned above and more besides) let us know. Pete PS Rob/all, the Microsoft link for "WIN32 API Constant Declarations"=20 http://members.tripod.com/~JJProg/win32api.zip (1995) is dead. >> >> With one single set of includes it would make the use of Euphoria = for >> >> Windows soooo much easier. An actual example might convince more readily than such a blanket statement. ----=_6es0iv83csi4qi5h6ad975116go7iip3v1.MFSBCHJLHS Content-Type: application/octet-stream; name=ppconst.ZIP