home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.alstevens.com
/
2014.06.ftp.alstevens.com.tar
/
ftp.alstevens.com
/
quincy99
/
README
< prev
next >
Wrap
Text File
|
2000-08-11
|
5KB
|
110 lines
Quincy 99 Build 0015, March, 2000
-------------------------------------
Quincy 99 is a Windows 9x and NT hosted Integrated Development Environment (IDE)
front end for C/C++ compilers.
I originally developed the ancestors of Quincy 99 to accompany a C++ tutorial book
and as a project for the C Programming Column of Dr. Dobb's Journal. Quincies 96 and
97 supported development of Win32 console applications only. Quincy 99 supports
development of Win32 console and GUI applications.
The Compilers
-------------
As currently configured, Quincy 99 works with the gcc Mingw32 2.95.2 C/C++
compiler suite.
Mingw32 (Minimalist GNU for Windows 32) is a version of the GNU gcc C/C++
compiler that uses the Win32 runtime DLLs.
See http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ for details.
The INSTALL file explains where to get the compiler files and how to install
them so that they work with Quincy 99.
The Tools
---------
Quincy 99 uses a grep program that I downloaded and modified slightly to make it work
as a program launched from the IDE.
Quincy 99 uses the resource compiler and editor tools that accompany the LCC-Win32 C
compiler suite, which you will find at http://www.cs.virginia.edu/~lcc-win32/.
The install.txt file explains where to get the tool files and how to install
them so they work with Quincy 99.
Source Code
-----------
The source code for the Quincy 99 IDE and the grep tool are available in the
quincy99src.zip file in the ftp directory where you found this file.
Quincy 99 is an MFC application compiled with MS VC++ 5.0
The grep program's source code is organized into a Quincy 99 project.
The source code for the C/C++ compilers and the resource compiler and editor tools
are available from the sites where you download them.
E-Mail Notification of New Builds
---------------------------------
If you wish to be notified by e-mail whenever I post a new Build to the ftp site,
send me a message at alstevens@midifitz.com identifying yourself as a Quincy tester.
If you send a bug report or other comment, I'll add you to that list unless you
ask me not to. If you want off the list, send me a message saying so. This is a
manual operation rather than an automatic mail list, so you don't have to use
subscribe/unsubscribe or other such protocols in the message.
Bug Reporting
--------------
Please install and use Quincy 99 and report bugs to me at astevens@ddj.com.
You can send your comments and criticisms to that address as well. I might
ask you to send some source code so that I can reproduce a bug. Please do not send
source code, data files, or screen shots unless I ask for them.
Please include the following information with all bug reports:
1. The steps required to reproduce the bug. Please be specific.
2. The symptom that the bug exhibits. Once again be specific.
3. The build number from the Help/About dialog.
4. The gcc version number from the Help/About dialog. Depending on when you download
the compiler, you might have a version that is newer than the one I have tested with.
5. If you get an error dialog, include the text from the dialog. Some diagnostic dialogs
include a lot of text. Just copy the first line or two. If I need more, I'll ask
for it.
6. A reliable way that I can reach you via email.
Things Fixed or Added in Build 0016
-----------------------------------
1. You could not install Quincy 99 or the compiler in a subdirectory with spaces
in the path specification. You could not compile a program in such a subdirectory
or have spaces in the program's source code file name. These problems are fixed.
2. Some symbolic information was left in executable modules even when debugging
information was not included. Added the -s option to the linker command to strip
these data from the binary.
Known Problems with Build 0016
------------------------------
1. Quincy 99 uses the Win32 CEdit control for its editor and cannot read source code
files larger than something less than 32K bytes. I am working on an improved editor
class with macros and full undo/redo. If you want to play with the editor in a
standalone version, you can download it from http://www.midifiz.com/alstevens/editor.
2. Inserting and deleting lines in the Editor does not update affected breakpoints.
3. Under certain elusive conditions, Quincy fails to observe that you have changed a
header file in memory that a source file in the project includes. The build proceeds
without first saving the changed header file. You should manually save any .h files
before building as a precautionary measure. If anyone can reliably reproduce this
problem, please let me know.
4. Cannot watch or examine a function pointer; Quincy always reports ??.
Al Stevens
astevens@ddj.com