Re: [Openocd-development] RFC: libopenocd strategy

[Rick Altherr]

On May 12, 2009, at 5:48 PM, Zach Welch wrote:

On Tue, 2009-05-12 at 17:21 -0700, Rick Altherr wrote:
[snip]

I had mentioned this a while back.  I've been thinking through the
approach and I'm slowly settling on a C++ implementation that would
essentially be a rewrite.  That said, I believe an autoconfig
mechanism could be done on the current implementation, but it would

for my idea.

probably be pretty difficult. I'll start drafting the formal proposal

Assuming you agree that a C++ implementation amounts to a new project,

a new mailing list and SVN repository).  I would subscribe and might

guide as much as any design or implementation proposals. ;)

Personally, I think this list is starting to see enough traffic about
the existing implementation that discussions of a new C++ branch here
will cause confusion that affects the community's focus and direction.
While announcements would be okay, I think we need to show a concerted


Cheers,

Zach

I think you might be better off starting a new project on berliOS (with even be talked into contributing, but I would want to see the C++ style effort on producing high-quality release of the existing implementation.

--
Rick Altherr
kc8...@kc8apf.net


 -- Unsigned

I agree. Of course, it is also possible to do the autodetection in C, but it would still require a pretty significant infrastructure change. Either way, this would be a long term project that should be done as a branch or as a new project. I suspect it would be better to do as a branch as it isn't _really_ a new project and much of the code for targets and interfaces would reused. At this stage though, any discussions would be merely about the proposal and what we want to do longer term. It should in no way impact the progress on current releases or projects. "He said he hadn't had a byte in three days. I had a short, so I split it with him."

smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development