Murphy

Just a note that commit MurphyMc/riplpox@c4d9272 in this PR addresses the main issue of #4 (-1 is not the correct value to represent NO_BUFFER) in the correct way for current...

@Huangmachi I think it's impossible to say without more information.

@humikahout It looks to me like your issue is unrelated to this pull request. It looks like you're using a POX component that isn't part of the standard POX distribution...

You need more than just shortest paths between nodes. At the minimum, you also need a scheme for mapping packet addresses to nodes. And then you need to actually install...

I hadn't thought of the macro approach, but there *are* variadic macros! They've historically had a problem in many cases when being called with zero arguments, but GCC has long...

Does this change anything with respect to using the fat arrow operator on such methods from within Rogue? That's the thing that occurs to me might lead to breaking something...

Just to see if I'm understanding, the proposed solution is: 1. We change routines to be GLOBAL METHODS on Global 2. If you ever apply fat arrow to a GLOBAL...

Looking back through the commit messages, it looks like the tcp branch expected to be run on Qooxdoo 5.0.2. Maybe try something closer to that? Also, you say there's no...

Actually, I think your basic problem is running the tcp branch in the first place. It was never really meant for general use, and the normal apps like the topo...

Hmm... I think it depends on what you wanted to do with it. I think if you just wanted to get it working such that you could feed it terminal...