<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>No guarantees on any of this imho. Nor the extension. The files are usually temporary. What are the magic bytes for .c? What is the purpose here? We could add 4 ignored bytes or even a guid but it'd be a waste.</div><div><br> - Jay</div><div><br>On Jun 12, 2015, at 7:51 AM, Elmar Stellnberger <<a href="mailto:estellnb@elstel.org">estellnb@elstel.org</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
<div class="moz-cite-prefix"><br>
Thanks a lot Rodney and Jay;<br>
that will certainly help my implementation.<br>
<br>
So far all *.mc files found on my machine have the<br>
following signature:<br>
16_FD,00,01,{00}<br>
<br>
except a few text - .mc from PM3 which start<br>
alltogether with "begin_unit". <br>
<br>
Rodney, do you believe that I can rely on the 4th byte<br>
to be zero as generated by the Modula-3 middle end. -<br>
or would anyone be ready to uphold such a guarantee<br>
for the future?<br>
<br>
Anyone here who has applied "od" on an .mc generated<br>
by a very recent compiler? - do they start with<br>
16_FD,10,01,?00?<br>
<br>
Most binary file types would guarantee a header of at<br>
least 4 Byte and it should be more straight forward and<br>
secure to check 32bit instead of 24bit if possible.<br>
<br>
Any suggestions?<br>
<br>
<br>
<div class="moz-cite-prefix">Am 10.06.15 um 02:21 schrieb Rodney
M. Bates:<br>
</div>
<blockquote cite="mid:55778303.3010009@lcwb.coop" type="cite"> <br>
<br>
On 06/09/2015 03:02 PM, Elmar Stellnberger wrote: <br>
<blockquote type="cite">What are *.mc - files?
<br>
They appear in TARGET - directories;
<br>
most of them are just called _m3main.mc but some of them have
other names.
<br>
<br>
I ask because I am writing a program which should recognize
and clear object files.
<br>
It does not seem to be sufficient to check for uppercase
directories which are located together with an src directory.
<br>
<br>
Usually files of a specific type start with a 32bit magic;
<br>
however the mc files all have different starting sequences.
<br>
<br>
Is there still a straight forward way to recognize an .mc file
just by its binary content?
<br>
<br>
</blockquote>
<br>
They will start with either 16_FD 16_00 16_01, produced by older
versions of cm3, <br>
or 16_FD 16_10 16_01, produced by a
very recent head compiler. <br>
Ignore the 4th byte. <br>
</blockquote>
<br>
<br>
Am 09.06.15 um 22:14 schrieb Jay K:<br>
</div>
<blockquote cite="mid:COL130-W2127E60FC8149B05469DE1E6BE0@phx.gbl" type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">
<div>ps:</div>
<div><br>
</div>
<div> foo.m3 => foo.mc => cm3cg => foo.ms => as
=> foo.mo </div>
<div> foo.i3 => foo.ic => cm3cg => <a href="http://foo.is">foo.is</a> => as
=> foo.io </div>
<div><br>
</div>
<div> again, see cm3 -keep, err better yet, cm3 -keep -verbose </div>
<div> You can see it running cm3cg and as and rm.</div>
<div><br>
</div>
<div><br>
</div>
<div> - Jay<br>
<br>
</div>
</div>
</blockquote>
<br>
</div></blockquote></body></html>