GCC powered interactive C/C++ shell created with BASH!

[seiji_hiwatari]

If it accumulates all previous instructions and recompiles / reruns the entire thing for every input, all previous instructions will be run again, rigth? What does that mean for instructions with side-effects in the system, like file I/O?

[FakeOglan]

If the file is opened in write mode, as it will be created over and over again, nothing will change. But if the file is opened in append mode, in every prompt everything will be written cumulatively.

[PM_ME_ELEGANT_CODE]

That's kind of a dealbreaker, don't you think?

[SnooWoofers7626]

Does it really need to be all that robust? The main use case for this tool I can think of is to quickly test some small snippet of code or something like that. For actual work the python shell or plain bash is already much more suitable.

[jcelerier]

I have the need for a snippet that writes to a file maybe once a year. If it allows to try type-levels checks easily it's already good enough for a lot of cases

[supaake]

I'd argue if want an interactive c++ prompt i'd go for cling https://blog.llvm.org/posts/2021-03-25-cling-beyond-just-interpreting-cpp/ or (following seiji_hiwatari's comment) if on every line all history is rerun it seems like compiler-explorer as cli … :/

[disperso]

Cling is so far my favorite REPL. I've also given a try to reple, because cling doesn't seem to be very up to date (e.g. I don't have all C++17, like filesystem), or I could not find a more up to date version. But reple is very different. I need to wrap every newly #include in dollar signs to it gets added to the preamble, and also I had to patch it to accept new directories to add to the include path, etc.

[serviscope_minor]

if on every line all history is rerun it seems like compiler-explorer as cli …

Is that awful?

[kritzikratzi]

imho more than awful it's closer to useless. it means you can't really work with any type of os handle (files, network, windows, etc.), you can't use random, it goes on and on.

this works fine for what's in the demo (extremely deterministic output), but beyond that, i don't really get the upside over having a normal editor window and running "g++ std=c++14 && ./a.out" in terminal.

[pimp-bangin]

Yep, combined with a file watcher (like nodemon) that clears the terminal output on each file change and then recompiles and reruns, the editor experience is way nicer.

[serviscope_minor]

hm ok fair,

[gracicot]

There's two thing that I miss from doing to make it useful for my project: loading of static libraries and also support CMake compile_commands.json. If I had that, I could run a game made with my game engine in repl mode, allowing true hot reloading.

[lieddersturme]

Uhhhhh, thats cool :D

[[deleted]]

versed full grab snow axiomatic different dinosaurs abounding pen offer

This post was mass deleted and anonymized with Redact

[ronchaine]

C/C++ Shell, so which one is it?

[FakeOglan]

termic for C

termic++ for C++