Re: struct tail array, compare and segv

Kevin Ryde <[EMAIL PROTECTED]> writes: > Neil Jerram <[EMAIL PROTECTED]> writes: >> >> "tail array not allowed if struct has a zero length layout" > > You don't think "unless ends in R,W,O" is enough to exclude an empty > layout? The aim, slightly, is to hint at the solution within the > error me

Re: struct tail array, compare and segv

Neil Jerram <[EMAIL PROTECTED]> writes: > > "tail array not allowed if struct has a zero length layout" You don't think "unless ends in R,W,O" is enough to exclude an empty layout? The aim, slightly, is to hint at the solution within the error message, for the benefit of those not 100% up with ho

Re: struct tail array, compare and segv

Kevin Ryde <[EMAIL PROTECTED]> writes: > I'm looking at this to allow non-zero tail array only when the layout > provides for it. I think all the internal uses of structs have no > tail array (and a zero size) so that should all be ok. Dunno if > anyone else might have used the tail size to get

Re: struct tail array, compare and segv

Hi, Kevin Ryde <[EMAIL PROTECTED]> writes: > I'm looking at this to allow non-zero tail array only when the layout > provides for it. I think all the internal uses of structs have no > tail array (and a zero size) so that should all be ok. Dunno if > anyone else might have used the tail size to

Re: struct tail array, compare and segv

I'm looking at this to allow non-zero tail array only when the layout provides for it. I think all the internal uses of structs have no tail array (and a zero size) so that should all be ok. Dunno if anyone else might have used the tail size to get some sneaky extra space. Sounds like the wrong

Re: struct tail array, compare and segv

Hi, Kevin Ryde <[EMAIL PROTECTED]> writes: >> but their semantics are a >> little fuzzy to me. In particular, I don't understand why the size of >> the tail array can be specified in both `make-vtable-vtable' and >> `make-struct': What does that mean? > > Nosing around the code, I think make-vta

struct tail array, compare and segv

Brought across from bug-guile ... [EMAIL PROTECTED] (Ludovic Courtès) writes: > > Actually, `scm_i_struct_equalp ()' should also compare the "tail > elements" (when there are tail elements), Is it as easy as using getting the size (of each) from "scm_struct_i_n_words", instead of just using the l