<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
<META content="MSHTML 6.00.6002.18124" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px">
<DIV>Peter:</DIV>
<DIV> </DIV>
<DIV>We need to make sure to add information about cm3IDE.</DIV>
<DIV> </DIV>
<DIV>The users guide can be found at: m3-sys\cm3ide\UsersGuide\CM3_IDE_UsersGuide.pdf</DIV>
<DIV> </DIV>
<DIV>Some of the environment variables you describe have to do with cm3IDE.</DIV>
<DIV> </DIV>
<DIV>Here is a list:</DIV>
<DIV> </DIV>
<DIV>CM3_IDE_HOME = env var for root of home folder</DIV>
<DIV>HOME = alternate home folder root, if CM3_IDE_HOME not supplied</DIV>
<DIV> </DIV>
<DIV>The following variables are expected to be defined in the CM3.CFG file:</DIV>
<DIV> </DIV>
<DIV>INITIAL_CM3_IDE_BROWSER = full path to the web browser that should be used with cm3IDE</DIV>
<DIV>INITIAL_CM3_IDE_EDITOR = full path to the text editor that should be called by cm3IDE</DIV>
<DIV>BUILD_DIR = NT386, HPPA, etc.</DIV>
<DIV>PKG_USE = full path to the public package root, e.g. /cm3/pkg</DIV>
<DIV>DOC_INSTALL = full path to the documentation root, e.g. /cm3/doc</DIV>
<DIV> </DIV>
<DIV>If the first 2 are not defined, cm3IDE will prompt user on command line to provide these the first time it is run. Thereafter, it saves the information in its config file that it places in the CM3_IDE_HOME folder.</DIV>
<DIV> </DIV>
<DIV>If the last 3 are not defined, cm3IDE tries to construct them using heuristics. If not successful, the program will abort.</DIV>
<DIV> </DIV>
<DIV>cm3IDE requires that is "examples" folder be located off the installation root, e.g., cm3/examples. If examples is not found, cm3IDE will still run, but it will not be able to offer up any examples.</DIV>
<DIV> </DIV>
<DIV>In an environment that allows spaces in filenames, such as Windows, you can run into problems if any of the paths defined in these variables have embedded spaces. On Windows, you can get around this problem by using the short 8.3 name equivalent.</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Randy</DIV>
<DIV><BR>>>> Peter Eiserloh <eiserlohpp@yahoo.com> 12/2/2009 12:01 PM >>><BR>Hi all,<BR><BR>It has been more than half a year since I last looked at the<BR>CM3 manual page. I am now looking at the it in preparation <BR>for the release of version 5.8, and noticing some deficiencies.<BR><BR>I asking for help in identifying any further places it is lacking.<BR>I can integrate any feedback into a revised manual page, and<BR>submit an updated version back to the archives.<BR><BR><BR>Currently identified deficiencies: <BR><BR>o The manual page should explicitly state which version of the<BR> compiler it documents.<BR><BR>o The sub-section "Expected Directory Structure" needs a better<BR> discussion, especially an introduction.<BR><BR>o The discussion of mode option "-ship" mentions environment<BR> variable CM3_INSTALL_ROOT, yet in cm3.cfg we set INSTALL_ROOT<BR> without the "CM3_" prefix. This should be resolved.<BR><BR> ** What is the exact meaning of these two? Is one recognized<BR> by the compiler, and the other by the supporting quake<BR> code?<BR><BR>o The ENVIRONMENT section does not mention CM3_INSTALL_ROOT<BR> at all. Add a discussion about both INSTALL_ROOT, and<BR> CM3_INSTALL_ROOT.<BR><BR> ** Am I missing any other environment variables?<BR><BR>o Missing command line options for the compiler:<BR><BR> - I currently have "-g", but no discussion of -gstabs.<BR> No discussion about not supporting DWARF (or do we?).<BR><BR>o Compiler unique language features, (i.e., pragmas). The<BR> reference books (Nelson, and Harbison) give a list of <BR> suggested pragmas. The manual page should list the ones<BR> supported by the CM3 compiler explicitly, and show their<BR> syntax.<BR><BR> ** Can someone list for me the pragmas supported by the<BR> current (5.8.4) compiler.<BR><BR>o Should list any limitations of either the compiler, or<BR> the library suite provided with the compiler. <BR><BR> For example, the WIDECHAR is limited by its 16-bit size<BR> to only a portion of the unicode character set <BR> (the basic multi lingual plane), whereas a unicode <BR> character is 20-bits, and we would need either a <BR> 24-bit or 32-bit sized type to contain it all.<BR><BR> ** Are there any other known limitations of the compiler,<BR> or library suite?<BR> - length of identifier?<BR> - length of TEXT (ie, memory)<BR> - length of filenames, or pathname <BR> (some architectures may have differences, <BR> ie MS-Windows).<BR><BR>o There should be a discussion of the @m3XXX runtime<BR> library command line options.<BR><BR>o There should be an EXAMPLE section, with example <BR> source code (Hello world), along with supporting <BR> m3makefile.<BR><BR><BR>+--------------------------------------------------------+<BR>| Peter P. Eiserloh |<BR>+--------------------------------------------------------+<BR><BR><BR> <BR></DIV></BODY></HTML>