<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Jay,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>My recollection on HPUX is that the K&R cc was provided
mainly just to rebuild the kernel and that if you wanted to do any real C
development, HP stood ready to sell you an ANSI C compiler. We purchased the
ANSI C, but still had to use the K&R for kernel adjustments. But, this was
many years ago (circa HPUX v9).<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Randy<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> jayk123@hotmail.com
[mailto:jayk123@hotmail.com] <b>On Behalf Of </b>Jay K<br>
<b>Sent:</b> Monday, August 23, 2010 5:52 PM<br>
<b>To:</b> Olaf; m3devel<br>
<b>Subject:</b> Re: [M3devel] main in C or not?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>Hm. Interesting subtle angle you point out.<br>
I have seen very few systems with ld but not cc. e.g. OLPC default install.<br>
My HP-UX/hppa machine came with only a K&R cc.<br>
Irix might have come with no official cc, but hunting around I found one that
worked well enough to build gcc.<br>
AIX maybe also.<br>
We could potentially call ld directly.<br>
But in general I don't write the configuration files that way, they run
cc for linking.<br>
*.c is used a bunch in m3core but not much else.<br>
<br>
<br>
On the other hand:<br>
cc is fairly ubiquitous.<br>
We have a "plan" for a "new distribution format"
that will require cc -- users will build more of the<br>
system. Though we'll still provide binaries for some systems.<br>
<br>
<br>
I'm *really* interested in a C-generating backend, which will subsume this.<br>
Except perhaps systems like NT386, and maybe we'll expand that set.<br>
I'm becoming increasingly frustrated with the gcc backend.<br>
<br>
<br>
I can compromise and leave the code in m3linker, but I still like the change in
cm3 where the configuration<br>
is ignored.<br>
<br>
<br>
I'll still go ahead and make the C code typesafe via ANSI prototypes.<br>
(potentially breaking HP-UX/hppa, but when I get back to that system
I'll probably #ifdef<br>
all the breakage, or require an ANSI compiler such as gcc; I assume nobody
really<br>
cares about K&R).<br>
<br>
<br>
Generating main in C seems to help some platforms, e.g. SOLgnu, SOLsun,
SPARC32_LINUX,<br>
but I admit I didn't fully debug these. And then, removing variations among
configurations, I like.<br>
But that can be achieved via the small change for now and leaving the support
in.<br>
<br>
<br>
- Jay<br>
<br>
> Date: Mon, 23 Aug 2010 13:57:01 +0200<br>
> From: wagner@elegosoft.com<br>
> To: m3devel@elegosoft.com<br>
> Subject: Re: [M3devel] main in C or not?<br>
> <br>
> Quoting Jay K <jay.krell@cornell.edu>:<br>
> <br>
> > There has long been a configuration variable: MAIN_IN_C.<br>
> ><br>
> > I propose that main always be in C. I made that so already, a small
change.<br>
> ><br>
> > I further propose that the support for main to not be in C be
removed.<br>
> ><br>
> > "Not in C" is "generating it via the backend",
directly an .obj for NT386, or<br>
> > going through the gcc backend for Posix.<br>
> ><br>
> > Furthermore, I'll cleanup the C to be more typesafe by using ANSI C.<br>
> ><br>
> > I have this change about ready.<br>
> ><br>
> > I don't think avoiding C is valuable and I'd rather have fewer <br>
> > configuration variables.<br>
> > Pick one approach that works reasonably always.<br>
> <br>
> This requires that every user must have a C compiler in addition to<br>
> cm3. I thought the default was not to generate C, and just require<br>
> a C compiler for special runtime support.<br>
> <br>
> I'm not sure if this really a valid argument for the systems we support<br>
> though, as we also need a system linker, and that is probably bundled with<br>
> the C compiler in a development package.<br>
> <br>
> Olaf<br>
> -- <br>
> Olaf Wagner -- elego Software Solutions GmbH<br>
> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany<br>
> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95<br>
> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin<br>
> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr:
DE163214194<br>
> <o:p></o:p></span></p>
</div>
</body>
</html>