ECOE - In terminal Linux object editor

[faissaloo]

Why I made this:
- I needed an excuse to learn C
- There only seem to be IDEs for ENIGMA/GM and so I wanted to start breaking things up into smaller programs so that they could be easily swapped out
- I hate Java... But I hate proprietary software more, which meant I had to use LGM... But openJDK doesn't work with xmir so I still have to use X11 and that means I have to live with screen tearing, eugh...
- Every ENIGMA/GM IDE seems just horrible for my workflow
- I wanted code actions to open in a code editor of my choosing
https://github.com/faissaloo/ECOE



As it is my first C project I would very much appreciate anyone who could tell me how bad my code is

[Goombert]

I understand your concerns and I actually really like your tools. This is absolutely great and I think these tools could be very useful. I've always maintained the position that every IDE and tool is potentially useful because it all depends on what the job is that needs done.

I actually wanted to create more command line tools for ENIGMA and I started with a CLI to build GMX projects once, but it has since broken:
https://github.com/enigma-dev/enigma-dev/tree/master/CommandLine/programs/emake

So for one don't feel bad, your code can't possibly be as bad as mine was. I hacked that thing together and I wasn't very good back then. Since I've advanced a little more I try to stick to formatting code properly and doing things correctly the first time. Really the most important thing is consistency and clarity in your code.

[TheExDeus]

Code looks okay, but I don't like C so I cannot give you many tips. I personally use C++ everywhere, and specifically modern C++. The "proper" way to use C++11 and newer actually make it look like more to python than C (C++14 guidelines being a good resource), so I enjoy the new C++ more. It would probably make your code smaller.

[faissaloo]

So for one don't feel bad, your code can't possibly be as bad as mine was. I hacked that thing together and I wasn't very good back then. Since I've advanced a little more I try to stick to formatting code properly and doing things correctly the first time. Really the most important thing is consistency and clarity in your code.

Thanks, I'll keep that in mind!

Code looks okay, but I don't like C so I cannot give you many tips. I personally use C++ everywhere, and specifically modern C++. The "proper" way to use C++11 and newer actually make it look like more to python than C (C++14 guidelines being a good resource), so I enjoy the new C++ more. It would probably make your code smaller.

I didn't feel like the object orientation of C++ would really be useful for ECOE, I wanted to keep it as lightweight as reasonably possible so I felt like C was the best choice for that.

[Goombert]

I can see why he would choose C over C++. One is that C++ has no standard ABI. Thanks to Rusky and DaSpirit I am starting to like Rust. I also hate every Windows port of GCC. Rust has reached stable 1.0 now so it is something to consider. It's nice to be able to return multiple values and be more expressive than C++.