Jeff Waller

Hey, thanks! As far as dims, I kinda brought it on myself as I'm trying to remain agnostic as much as I can, and therefore as using **MemoryDataLayer**. Potentially I...

Seems like that would work, what caused it to be placed there in the first place? Maybe the default should be populated in the conf directory from the outset.

Since the generated parsers are modular. As a workaround, create a simplistic lexer and use it's output as input to the for-real one e.g: elideWS.pegjs: s = input:(whitespaceCharacter / textCharacter)*...

So the difference is that you want to distinguish when the overall engine is operating in lexer mode (whitespace is significant) and when not (whitespace is ignored). Is there a...

On Apr 23, 2014, at 2:54 PM, Sean Farrell [email protected] wrote: > @waTeim Actually no. > > So we agree. The traditional approach is sufficient. There’s no need to have...

Oh man, free response section! I have a lot to say, so sorry for the length. 1) For the TL;DR people, if I could add any peg elements, I wanted,...

I don't think so. Are you sure because that approach has a lot of problems. It's not really the algorithm as documented in Wikipedia, it should be kxn and be...

Yea, that's more efficient if the number of rows^2 is storable, but in this case, nope. And like I said, this isn't even the largest of the datasets. I was...

Ok I was wrong about only 1 MIG instance per pod, expect an update to include support for multiple

Reworked MIG detection. Allows for multiple host and MIG instances. Some API calls only work on the hosts, tested for that. Saved it all in a deviceMap and saved that...