thomcc / asmcc Goto Github PK

Straightforward enough. Probably should just be a json file named ~/.asmccrc or something. It would be nice to also allow ~/.asmcc/config.json, which would allow users to put templates in the ~/.asmcc folder.

Probably just GCC, maybe ICC eventually. This would require a way of getting the compiler to use from the user.

The hard thing here is figuring out which compiler they've selected (e.g. if they gave us an alias) and translating the flags to them, and using additional flags when they're helpful. E.g. verbose output for GCC would be enabled by -fasm-verbose, but -Wa,ahl should probably be passed too. ICC uses -fsource-asm.

I don't use gcc or icc on a regular basis so I'll probably only do this if there's interest.

Right now when compilation fails, you're given the option of editing the code you entered. This is already better than it used to be (where hopefully you had copied it into your clipboard), but it still is imperfect.

If you forgot a flag you wanted, (for example, your code uses exceptions and you didn't enable them) you need exit and try again, which is annoying. Even worse is when you forgot to enable -C and you lose the code after the assembly is generated (or maybe this just means -C should be on by default).

I'm not sure I'm going to add this unless I come up with a way to do it simply (without requiring complete restructuring of the code or the addition of a complex parser).

Probably just requires moving some files around and adding some metadata.

If the user gives a file with -i, we should try to detect the language if they don't specify a language. Unknown or ambiguous cases should be ignored. When config files are added, users should be able to disable this behavior.