[01:39] *** preteran_ joined [01:40] *** preteran_ left [01:48] *** ilbot3 joined [02:05] *** zakharyas joined [03:34] *** Ven_ joined [03:49] *** Ven_ joined [05:43] *** domidumont joined [05:48] *** domidumont joined [05:49] *** Ven_ joined [07:04] *** brrt joined [07:55] had so much to do yesterday i forgot the solution i had cooked up :-( [08:10] *** brrt joined [08:24] this "work" thing is overrated [08:26] :-( [08:26] yes.... [09:15] *** zakharyas joined [10:54] jnthn: can you look at moar PR #416? https://github.com/MoarVM/MoarVM/pull/416 [11:06] Hm, that error could be a bit clearer/explanatory perhaps [11:06] It'd be nice if it included the type name too [11:06] right, as commented, the nqp-j equivalent has the class name, but i'm not sure how to do that on moar [11:07] like, we don't have the convenient Ops.typeName afaict [11:07] about explanatory... well, the test i pushed only checks the message for "no fields" [11:08] i suppose we could explain why no fields are a bad thing for a CStruct [11:08] Commented on the ticket [11:09] Well, commit [11:10] right, so that's to be a sprintf with %s for st->debug_name or so i gather? [11:10] MVM_throw_exception_adhoc works printf-y :) [11:10] So just pass it as an extra arg [11:10] ah, okay [11:11] It's C but we try to make it at least a tiny bit convenient :) [11:14] lunch, bbiab [12:37] *** domidumont joined [13:28] *** zakharyas joined [13:43] *** FROGGS joined [13:57] *** domidumont joined [15:29] *** patrickz joined [15:48] *** dalek joined [15:56] *** FROGGS joined [16:31] *** domidumont joined [18:12] *** Dunearhp joined [18:19] *** Dunearhp joined [18:52] *** domidumont joined [22:35] *** japhb joined [22:40] rakudo NativeCall tests fail on several architectures https://lists.alioth.debian.org/pipermail/pkg-rakudo-devel/2016-September/000970.html [22:41] when I try with a MoarVM build against libffi, I have some failure for amd64 and i386: https://lists.alioth.debian.org/pipermail/pkg-rakudo-devel/2016-September/000971.html [22:42] i386 surprises me a bit [22:42] libffi fails don't in so far as it's had a lot less testing [22:42] I'm suspecting either alignment or endianness [22:52] *** TimToady joined