Should I ever look into this project again, I foresee
nasal demons and bleeding eyes... seriously, you seem to be determined to break both ABI compatibility (for any and all OSes other than perhaps your own) and the C language standard at every turn.
At this point, you'd be better off designing a whole new language - and yes, I am fully aware of how large a project that would be - rather than folding, spindling, and mutilating the existing language on a whim. While you can make a dialect of C if you like - it isn't as if there's some sort of Parser Police who would hunt you down for it - if you then claim that it is still compliant C, then you are going to anger anyone else using your hybrid language expecting it to follow the standard language's rules.
As for ABI compliance, well, if you are bound and determined to ensure that your compiler will never interop with any existing libraries, ever, then you do you, I guess, but don't be surprised when it blows up in your face.
Of course, all of this is predicated on your success in compiler development, and given what you've done with that so far, I think everyone save you can see that this is several bridges too far.
Let me ask you again: have you read any of the books or tutorials (or watched any of the videos)
we've recommended in the past, and are you applying any of what they say? Please, just give us
some sort of answer on this, since as things stand, we don't know what you know, and don't know how to give you any more advice.
I do know that,
from your own statements, you've read the old Crenshaw
"Let's Build a Compiler" tutorial, yet so far you seem to be ignoring most of what it says, which puzzles me to no end. It speaks to something I've
said before: if you write and act like a crackpot, and there is no evidence that you know or understand what you are saying, we can only conclude that you
are a crackpot even if you aren't because that's what the evidence is pointing to.
That having been said, I have noticed that you haven't updated the ZIP file with your source code - and I'll address the matter of misusing Sourceforge shortly - which means that, even if you have made significant progress on your compiler (hopefully including fixing all of the problems I have previously mentioned) - we can't see any of that, so we can only base our opinions of your current progress on a single archive file from a year ago.
On that topic, you seem to have misunderstood the point of version control repositories such as Sourceforge. While it is possible - and distressingly common - for projects to upload a single archive there for quick download, the real intent of a site such as SF or Github is to serve as a host for your VCS repo. We've discussed this topic at length on this forum, as well as in the wiki, but let me repeat the point:
IF YOU DON'T USE A VCS, EVENTUALLY YOU WILL LOSE YOUR WORK, or worse, be unable to perform a regression on a hidden bug and have to scrap a whole section of existing code. While there are other ways to solve such problems, version control software is
designed to facilitate this, and using it should be a no-brainer.
Uploading a single archive file with everything in it doesn't count as version control. You
need to use something like Subversion, Git, or Mercurial, and use it
consistently. You need to ensure that only the source and resource files get included in the repo, not the object files and executables. You need to have the individual source files visible to anyone browsing your repo, so they can review it (and maybe contributed bug fixes and additional code, should someone want to bother). What you have now is a flat-out misuse of Sourceforge.
Take a look at some other people's code repos, both on SF and on other hosts, and see how they do things
correctly. On Sourceforge, a good example of how to use it with SVN is
FreeDOS, which I expect you are at least passingly familiar with. For GIT and Github, try
Mezzano OS. You should be able to see right away how they differ from what you are doing. Note that both of these hosting platforms have services which
automatically pack the latest code release into either a ZIP or a tarball, while at the same time allowing access to individual files through the version control systems.
Please, for your own sake, try emulating their approaches for this and any other projects you're working on.