[#7708] Bug in libsnmp-ruby1.8 — Hadmut Danisch <hadmut@...>

Hi,

8 messages 2006/04/11
[#7709] Re: Bug in libsnmp-ruby1.8 — Eric Hodel <drbrain@...7.net> 2006/04/11

On Apr 11, 2006, at 6:23 AM, Hadmut Danisch wrote:

[#7770] Re: possible defect in array.c — "Brown, Warren" <warrenbrown@...>

> rb_range_beg_len (in range.c) does set beg and len.

13 messages 2006/04/26
[#7771] Re: possible defect in array.c — "Pat Eyler" <rubypate@...> 2006/04/26

On 4/26/06, Brown, Warren <warrenbrown@aquire.com> wrote:

Re: possible defect in array.c

From: Hugh Sasse <hgs@...>
Date: 2006-04-26 18:28:11 UTC
List: ruby-core #7778
On Thu, 27 Apr 2006, Pat Eyler wrote:

> On 4/26/06, Jacob Fugal <lukfugl@gmail.com> wrote:
> > On 4/26/06, Pat Eyler <rubypate@gmail.com> wrote:
> > > good idea:
> > >
> > > *** array.c     12 Dec 2005 16:46:59 -0000      1.186
> > > --- array.c     26 Apr 2006 15:27:05 -0000
> > > ***************
> > > *** 2100,2105 ****
> > > --- 2100,2106 ----
> > >   {
> > >       VALUE item, arg1, arg2;
> > >       long beg, end, len;
> > > +     beg = 0;
> > >       VALUE *p, *pend;
> > >       int block_p = Qfalse;
> >
> > Actually, that'd be a syntax error in C. All variable declarations in
> > C must precede all other statements.
> 
> More proof that I'm not a C hacker.  I did compile after making the
> change and didn't see any errors from gcc:

Whilst considering details, are there any compilers around these
days that need the bigger things declared first, so they get byte
boundaries correct?  Or did that disappear when we left K&R C
behind?  OTTOMH I'm not sure about the relative sizes of these
(VALUE *, long, VALUE) anyway...

        Thanks
        Hugh


In This Thread