Benjamin Landers

The behavior is a little complicated. Based on my testing tonight psuedo-code for this would look like: ``` if current file is new / doesn't exist: grey out the assemble...

I don't understand how RARS would be much help teaching synchronization primitives; it would only be able to show uncontested accesses. It would probably take about a month of full...

Since you are looking at implementing multi-threading here are some of the issues that would be time sinks: - Registers currently use static variables so in order to have multiple...

I haven't made a program to check, but I am pretty sure RARS works properly with the `read` system call. Only the simplified reads use `readStringInternal`. > 2. Modify the...

You are absolutely right that STDOUT suffers from the same issue. > I apologize for the long description. I would add a branch and a pull request but every time...

Can you describe what is inconsistent? Is output not showing up? Showing up after a long lag? Showing up out of order? Relevant issues #80 and #108

Making a minimal api per your suggestion would be quite easy (I think). However, I would like to go a little bit beyond the minimum. But I haven't come up...

I have come up with a design I am pretty happy with. The bulk of the interface would be in a Program class as follows: ``` public class Program {...

> Is it possible to get register content after termination? With the proposed design thats pretty easy. It would be something like: ``` p.getRegisters().getValue("t0") ``` Instead of the ``` //...

One of the reasons is that string lookup already has to exist for the assembler. With that in mind, adding enums to represent each would make it more typesafe, but...