<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Am 12.06.15 um 22:10 schrieb Jay:<br>
</div>
<blockquote
cite="mid:77B51204-3A95-4747-8DFE-053B2D8FEC27@gmail.com"
type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<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>
</blockquote>
human readable text files do not need any magic<br>
but binaries do (though auto-generated text files<br>
by a program will need a header, too).<br>
<br>
A cm3 and middle end version numbers for a <br>
compatibilty check if not also a creation timestamp<br>
after the magic would be very beneficial, too.<br>
<br>
It is unprofessional and a bad habit to emit a binary <br>
stream without a header and versioning information.<br>
Have you never used a ready compiled cm3cg for <br>
compiling a new frontend? - There should be a<br>
middle end version number to check whether this <br>
is prone to fail (and possibly one trying to force<br>
application of cm3cg on a newer intermediate code<br>
stream. ).<br>
<br>
</body>
</html>