librelist archives

« back to archive

I'd like to help with C scut work

I'd like to help with C scut work

From:
Andy Lester
Date:
2011-10-13 @ 05:14
Hi, I'm Andy, and love git and I like to work on infrastructure parts of 
C-heavy projects.

Things I think every C project should have:

* Warnings maxed out as much as possible
* lint/splint make targets, with useful settings
* valgrind make targets, with useful settings

A lot of that is just slogging through lots of warnings getting things to 
a state where we don't get false alarms, and get actual 
compiler/lint/valgrind warnings when things go wrong.

Is the project interested?

xoxo,
Andy

--
Andy Lester => andy@petdance.com => www.petdance.com => AIM:petdance

Re: [libgit2] I'd like to help with C scut work

From:
Emmanuel Rodriguez
Date:
2011-10-13 @ 06:51
On Thu, Oct 13, 2011 at 07:14, Andy Lester <andy@petdance.com> wrote:
>
> Hi, I'm Andy, and love git and I like to work on infrastructure parts of
C-heavy projects.
Hi Andy,

I know that you're quite involved in the Perl community and so far
Perl doesn't have proper bindings for libgit2.

I could use some help with the Perl bindings for libgit2
(https://github.com/potyl/Git2). I don't have too much time to work on
the bindings so there's still some more work to do.

Don't be scared about the actual package name (Git2), that's a
provisional name that I picked until the bindings done.

-- 
Emmanuel Rodriguez

Re: [libgit2] I'd like to help with C scut work

From:
Andy Lester
Date:
2011-10-13 @ 14:28
On Oct 13, 2011, at 1:51 AM, Emmanuel Rodriguez wrote:

> I know that you're quite involved in the Perl community and so far
> Perl doesn't have proper bindings for libgit2.


I'm not sure I'd have time or know-how to pull that off.

xoa

--
Andy Lester => andy@petdance.com => www.petdance.com => AIM:petdance

Re: [libgit2] I'd like to help with C scut work

From:
Vicent Marti
Date:
2011-10-13 @ 14:35
Hey Andy,

we're certainly interested. Currently we max out our warnings on all
platforms, but we are still missing proper valgrind and lint targets.
The thing is that we are using CMake, so I'm not quite sure on how to
integrate those tools with it.

Either way, anything that improves the code quality of the project is
very much welcome. The perfect place to discuss this in depth is the
Issues section on GH [1]. If you open a issue regarding lint/valgrind
integration there, I'll assist you on everything I can.

Cheers,
Vicent

[1]: https://github.com/libgit2/libgit2/issues

On Thu, Oct 13, 2011 at 5:14 AM, Andy Lester <andy@petdance.com> wrote:
>
> Hi, I'm Andy, and love git and I like to work on infrastructure parts of
C-heavy projects.
>
> Things I think every C project should have:
>
> * Warnings maxed out as much as possible
> * lint/splint make targets, with useful settings
> * valgrind make targets, with useful settings
>
> A lot of that is just slogging through lots of warnings getting things 
to a state where we don't get false alarms, and get actual 
compiler/lint/valgrind warnings when things go wrong.
>
> Is the project interested?
>
> xoxo,
> Andy
>
> --
> Andy Lester => andy@petdance.com => www.petdance.com => AIM:petdance
>
>

Re: [libgit2] I'd like to help with C scut work

From:
Andy Lester
Date:
2011-10-13 @ 14:56
On Oct 13, 2011, at 9:35 AM, Vicent Marti wrote:

> we're certainly interested. Currently we max out our warnings on all
> platforms, 


One thing I'd like to look at is detecting warnings available.  Just 
looking at the differences between GCC 3.x and 4.7, there are many 
warnings available in newer compilers.  On the Parrot project, when you do
the initial configure, it sniffs out the compiler warnings available and 
flips on the good ones.

xoxo,
Andy

--
Andy Lester => andy@petdance.com => www.petdance.com => AIM:petdance

Re: [libgit2] I'd like to help with C scut work

From:
Andy Lester
Date:
2011-10-13 @ 14:39
On Oct 13, 2011, at 9:35 AM, Vicent Marti wrote:

> Either way, anything that improves the code quality of the project is
> very much welcome. The perfect place to discuss this in depth is the
> Issues section on GH [1]. If you open a issue regarding lint/valgrind
> integration there, I'll assist you on everything I can.


Sounds good.  I'll pull a fork and see what I can do.

I just didn't want to start some work and then get a "No, thanks, we're 
not interested", as has happened before.

xoxo,
Andy

--
Andy Lester => andy@petdance.com => www.petdance.com => AIM:petdance