On Tue, Feb 11, 2014 at 15:54:40 -0500, Brad King wrote:
> Why does each level in the openstack need to hold its "lookup"
> member? Can't everything be stored in-place in the work buffer?
< in-person discussion of the algorithm >
After looking at the implementation, it may not save much since we
On Tue, Feb 11, 2014 at 15:54:40 -0500, Brad King wrote:
> Why does each level in the openstack need to hold its "lookup"
> member? Can't everything be stored in-place in the work buffer?
> Each openstack level just needs to track the start character in
> the work buffer. When that level is close
On 02/11/2014 02:49 PM, Ben Boeckel wrote:
> dev/custom-parsers
cmMakefile::ExpandVariablesInString has long been ripe for
optimization. Thanks for working on it.
Why does each level in the openstack need to hold its "lookup"
member? Can't everything be stored in-place in the work buffer?
Each
