Re: [concordance-devel] Bumping soname for release, and language bindings

[Phil D. <ph...@ip...>]

Phil Dibowitz wrote:
> Stephen Warren wrote:
>> Phil,
>>
>> This is just a quick note recalling the fact that you were going to bump
>> the libconcord soname sometime soon before release. When this gets done,
>> don't forget to the ABI_VERSION value in libconcord.py.
> 
> Thanks, I would have forgotten libconcord.py.
> 
>> Also, aren't the Perl bindings sometime out of date relative to the new
>> IR learning APIs? I believe the Python bindings are fully up-to-date,
>> but I'll run another validation pass in the next couple days.
> 
> Ah, crap. Good call. Thanks.

OK, the perl bindings are up-to-date wrt the IR APIs, but there's one
glaringly ugly problem with the way I did it (see the commit from a few
minutes ago). I'd like to fix that before release.

I'd also like to wait for Doug's feedback... I leave for LA for a week on
Wednesday (I'll be at SCALE, so anyone attending SCALE drop me a line and
we'll meet up).

What this means is that 0.21 may not get out until the end of February...
but it's been like 6 months, so I figure 2 more weeks won't kill anyone.

-- 
Phil Dibowitz                             ph...@ip...
Open Source software and tech docs        Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"Never write it in C if you can do it in 'awk';
 Never do it in 'awk' if 'sed' can handle it;
 Never use 'sed' when 'tr' can do the job;
 Never invoke 'tr' when 'cat' is sufficient;
 Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming