Um yeah... I really don't mean to be disrespectful, but I don't
think this is the place to discuss terminology.
On Saturday, 28 December 2013 at 06:24:06 UTC, H. S. Teoh wrote:
We should just call it a newsgroup. Or a mailing list. I prefer
the
latter, since it's clear that once the mail is sent out, you
can't
"unsend" it to make further corrections.
Well, it does not really matter how we call it if do
On Sat, Dec 28, 2013 at 06:04:01AM +, Mike Parker wrote:
> On Saturday, 28 December 2013 at 01:02:54 UTC, Jonathan M Davis
> wrote:
> >On Thursday, December 26, 2013 05:02:48 Hannes Steffenhagen wrote:
> >>Sorry, I'm not sure how to edit posts
> >
> >It's not possible to edit posts. There are m
On Saturday, 28 December 2013 at 01:02:54 UTC, Jonathan M Davis
wrote:
On Thursday, December 26, 2013 05:02:48 Hannes Steffenhagen
wrote:
Sorry, I'm not sure how to edit posts
It's not possible to edit posts. There are multiple interfaces
to this
newsgroup (NNTP, mailing list, and web forum),
On Thursday, December 26, 2013 05:02:48 Hannes Steffenhagen wrote:
> Sorry, I'm not sure how to edit posts
It's not possible to edit posts. There are multiple interfaces to this
newsgroup (NNTP, mailing list, and web forum), and the ability to edit posts
would not work with that. So, replying to
On Thursday, 26 December 2013 at 05:01:08 UTC, Hannes
Steffenhagen wrote:
I'm not sure what's the cause and I don't know enough about
dmd's internals to make an educated guess, but I'm pretty sure
this is a bug in dmd and not in LuaD.
Indeed it is a DMD regression. I haven't been able to reduc
I'm trying to use the LuaD library right now... unfortunately,
I've run into somewhat of a roadblock.
This doesn't work (assertion failure in dmd's backend/cgcs.c:351,
which has apparently something to do with bitops... there's an
assert(0) there and I'm not really sure why).
import luad.a
Sorry, I'm not sure how to edit posts, it's 6am and I kinda
didn't get any sleep yet, so excuse me if I'm a bit confused
right now. The second example was supposed to be
state.globals.get!.
