Re: [Openocd-development] libopenocd... again

2009-12-05 Thread Øyvind Harboe
On Sat, Dec 5, 2009 at 8:43 AM, Zach Welch wrote: > On Fri, 2009-12-04 at 23:31 -0800, David Brownell wrote: >> On Tuesday 01 December 2009, Zach Welch wrote: >> > We should approach this problem as though we intend to eventually >> > decouple Jim from the core functionality and switch to a differ

Re: [Openocd-development] libopenocd... again

2009-12-05 Thread Zach Welch
On Sat, 2009-12-05 at 00:51 -0800, David Brownell wrote: > On Friday 04 December 2009, Zach Welch wrote: > > > > > That's a useful statement of the extreme, but note that it's in > > > two parts: decouple ... and switch. > > > > > > Decoupling is one of those things that's not fully understandab

Re: [Openocd-development] libopenocd... again

2009-12-05 Thread David Brownell
On Friday 04 December 2009, Zach Welch wrote: > > > That's a useful statement of the extreme, but note that it's in > > two parts:  decouple ... and switch. > > > > Decoupling is one of those things that's not fully understandable > > except in the context of concrete options.  Without seeing a f

Re: [Openocd-development] libopenocd... again

2009-12-04 Thread Zach Welch
On Fri, 2009-12-04 at 23:31 -0800, David Brownell wrote: > On Tuesday 01 December 2009, Zach Welch wrote: > > We should approach this problem as though we intend to eventually > > decouple Jim from the core functionality and switch to a different > > front-end language. > > That's a useful stateme

Re: [Openocd-development] libopenocd... again

2009-12-04 Thread David Brownell
On Tuesday 01 December 2009, Zach Welch wrote: > We should approach this problem as though we intend to eventually > decouple Jim from the core functionality and switch to a different > front-end language. That's a useful statement of the extreme, but note that it's in two parts: decouple ... and

Re: [Openocd-development] libopenocd... again

2009-12-03 Thread Zach Welch
On Thu, 2009-12-03 at 01:50 -0800, Zach Welch wrote: > On Tue, 2009-12-01 at 21:08 -0800, Zach Welch wrote: > > Hi all, > > > > Assuming a split between policy and mechanism can be addressed, OpenOCD > > will become much more usable as a proper library. One of the questions > > that needs resolut

Re: [Openocd-development] libopenocd... again

2009-12-03 Thread Zach Welch
On Tue, 2009-12-01 at 21:08 -0800, Zach Welch wrote: > Hi all, > > Assuming a split between policy and mechanism can be addressed, OpenOCD > will become much more usable as a proper library. One of the questions > that needs resolution is "how to install our header files". The answer > that we c

[Openocd-development] libopenocd... again

2009-12-01 Thread Zach Welch
Hi all, Assuming a split between policy and mechanism can be addressed, OpenOCD will become much more usable as a proper library. One of the questions that needs resolution is "how to install our header files". The answer that we chose for this will determine how much restructuring will be requi