<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Something seems off to me in the current implementation.<br>Like, I don't think the backends are ever informed of various "builtin" types, such as integer, word, char, widechar, boolean, mutex.<br>I hardcoded knowledge of them in parse.c and M3C.m3.<br>That seems wrong.<br><br><br>Either that, or they are used before they are defined -- which might not be avoidable in general, but could easily be avoided for most types.<br><br><br>Shouldn't m3front inform the backend via m3cg of these types?<br>It is doable using the existing interfaces? <br><br><br>More so, RTBuiltin.mx ought not exist, right?<br>Whatever data it contains should be built up like any other type data?<br>Part of the same problem?<br><br><br> - Jay<br> </div></body>
</html>