chaoticweg/c_irc

A basic IRC-like server and client built from the ground up. Major Assignment (final) for UNT CSCE 3600.001 (Systems Programming)

c_irc's Issues

Client-side: output wipes how input looks to user

Since input comes from stdin and output goes to stdout, input isn't actually wiped when a line is output to console. However, it looks bad.

This is definitely not a pressing issue and shouldn't be rushed for deadline, because it's above and beyond the requirements. Still, would be nice to have if we can get around to it.

Hopefully Relevant StackOverflow Q/A

Makefile does not create required directories that are ignored by Git

Makefile directs gcc to put the compiled binaries into ./bin, which is ignored by Git. Pulling a fresh copy of the repository and trying to make client or server will likely cause a "no such file or directory" error. This can be worked around by manually creating the directory with mkdir bin inside the top-level directory, but that's not good for a TA who is just trying to grade the code and move on to the next one.

The makefile rules for building client and server, respectively, should each check that $(OUTDIR) exists before running gcc.

Random LEAVE messages

Sometimes we get random user-less messages in the server console that look like >>> LEAVE: and nothing else.

^_lolwut

Repository structure does not match project requirements

More specifically, the project requirements state that the TAs should be provided with a README with compile/build instructions; or, ideally, a makefile that allows them to just run make and be provided with fresh binaries.

The easiest way to fix this would be to set the default rule in the makefile to create a new directory and compile all binaries into that one.

^{_{Christ, I hate BlackBoard's assignment submission system.}}

Add "file" command

Needs file [filename] command, per requirements.