HyperC

[laserlight]

This is how i see it.

So this means that you want HyperC to retain the notion of undefined behaviour. This means that the responsibility is on you to define HyperC rigorously, because whatever you miss out in this regard is undefined behaviour.

[Structure]

This means that the responsibility is on you to define HyperC rigorously

If you program with HyperC and you cause an error how is that my fault ?

If HyperC is the cause of the error i will fix it.

FYI rigorous is an understatement for my coding techniques.

[Structure]

Im still confused about the difference between undefined behavior and a mistake.

you want HyperC to retain the notion of undefined behaviour.

There should be some sort of structure and rules i think.

[laserlight]

If you program with HyperC and you cause an error how is that my fault ?

It isn't!

FYI rigorous is an understatement for my coding techniques.

You forgot to check the return value of fgets when providing an example in the C programming forum recently

But anyway, I'm talking about rigour of language specification, not code.

Im still confused about the difference between undefined behavior and a mistake.

Consider a common programming mistake:

int numbers[10];
for (int i = 0; i <= 10; ++i)
    numbers[i] = i;

In C, this results in undefined behaviour: the compiler is free to produce a program that does practically anything on that out of bounds assignment to numbers[10]. In other programming languages, this error might be well defined, e.g., perhaps the wrong assignment would cause an exception to be thrown, and this is guaranteed to happen.

Here's another common beginner's question in C:

int x = 0;
printf("%d\n", x++ + x++);

What's the output? In C, the answer is that the behaviour is undefined, so this is actually a mistake because of how sequence points/sequenced before/after work in C. In languages that don't have the notion of undefined behaviour, they might define it, so this would not be a mistake... or they might explicitly say that such use is an error, and hence require the compiler to reject the code with an error.

[Structure]

Importing shaders:

<c static const char* vertex_shader_source = ":$>shaders/vertex.glsl;";
<c static const char* fragment_shader_source = ":$>shaders/fragment.glsl;";

[Structure]

If anyone wants to actually try the compiler and give me comments that would be fun. I built the compiler for myself but thought it might be usefull to others. tbh i'm not trying to put it out there i'm fine using it myself but if you want try it out and help me build a better c i'm all ears.

[Hodor]

If anyone wants to actually try the compiler and give me comments that would be fun. I built the compiler for myself but thought it might be usefull to others. tbh i'm not trying to put it out there i'm fine using it myself but if you want try it out and help me build a better c i'm all ears.

Perhaps if it was open source then I'd give it a go. As for running a random .exe on one of my Windows computers... ?... yeah, no thanks I guess I could see if it works in Linux using Wine, but why?

[Structure]

Perhaps if it was open source then I'd give it a go.

go away.

As for running a random .exe

I understand this issue and people are scared of running .exe i get it.

[Hodor]

go away.


I understand this issue and people are scared of running .exe i get it.

Why not open source it? It's not as if it's going to make you a millionaire... I guess not anyway

[Structure]

Why not open source it?

If people want to use it and maybe if it works out i will open-source a bare bones version.

[Hodor]

If people want to use it and maybe if it works out i will open-source a bare bones version.

Ok, I want to use it

[Structure]

Ok, I want to use it

Hyper C Compiler

Let me know if you have any questions.

[Structure]

When compiling to .c at the top of the c file you should see a compiled with hyperc version. The current version is v5.

During the v4. process i came across some errors while adding new features.
Those have been fixed. So if you do come across an error make sure it is v5 as it may already be fixed.

[Structure]

A simple menu system:

<stdio.h>; <stdlib.h>; <conio.h>;

#@drawMenu() {
  with ink ;and "\n";
    "Menu ";
    "-------------";
    "[1] cls";
    "[2] dir";    
    "[esc] exit";
    "-------------";
  and;  
    "selection: ";    
  with;
  return getch();
};

@menu() {  
  switch (drawMenu()) {
    case '1':
      shell "cls";      
    break;
    case '2':
      shell "dir";
    break;
    case 27:
      exit(1);
    break;
    default:
      ink "Invalid Selection.\n";
    break;
  };
  menu();
};

@{ 
  menu(); 
};

[Salem]

TBH, all this belongs on a blog on your own forum, where people who are actually interested can follow your wandering thoughts.