Thread overview
Problems importing core.sys.linux.epoll
Sep 09, 2013
Mike Parker
Sep 09, 2013
Anthony Goins
Sep 10, 2013
Mike Parker
Sep 10, 2013
Mike Parker
Sep 11, 2013
goughy
Sep 11, 2013
Mike Parker
September 09, 2013
I'm experimenting with some Linux stuff right now and am currently working on something using epoll. But I've run into an issue where dmd just doesn't see anything in core.sys.linux.epoll. As a workaround, I've implemented my own declarations for the bits I'm using. I'm curious, though, if anyone else has encountered this as I've never seen anything like it. I get no errors at all about it not being able to find the module, just things like "epoll_event is undefined" and such. If I try something like this:

import core.sys.linux.epoll : epoll_event;

Then I get an error about the import not being found. Other modules in core.sys.linux import just fine.

If anyone else can verify this same issue, I'll file a bug report. Otherwise, any ideas on what could cause this?
September 09, 2013
On Monday, 9 September 2013 at 11:14:47 UTC, Mike Parker wrote:
> I'm experimenting with some Linux stuff right now and am currently working on something using epoll. But I've run into an issue where dmd just doesn't see anything in core.sys.linux.epoll. As a workaround, I've implemented my own declarations for the bits I'm using. I'm curious, though, if anyone else has encountered this as I've never seen anything like it. I get no errors at all about it not being able to find the module, just things like "epoll_event is undefined" and such. If I try something like this:
>
> import core.sys.linux.epoll : epoll_event;
>
> Then I get an error about the import not being found. Other modules in core.sys.linux import just fine.
>
> If anyone else can verify this same issue, I'll file a bug report. Otherwise, any ideas on what could cause this?

I get "undefined identifier" for everything in epoll.
DMD 2.63 (not latest) from debian download.
September 10, 2013
On 9/10/2013 3:38 AM, Anthony Goins wrote:

> I get "undefined identifier" for everything in epoll.
> DMD 2.63 (not latest) from debian download.

Thanks! http://d.puremagic.com/issues/post_bug.cgi
September 10, 2013
On Tuesday, 10 September 2013 at 01:52:14 UTC, Mike Parker wrote:
> On 9/10/2013 3:38 AM, Anthony Goins wrote:
>
>> I get "undefined identifier" for everything in epoll.
>> DMD 2.63 (not latest) from debian download.
>
> Thanks! http://d.puremagic.com/issues/post_bug.cgi

I meant http://d.puremagic.com/issues/show_bug.cgi?id=11002
September 11, 2013
On Monday, 9 September 2013 at 11:14:47 UTC, Mike Parker wrote:
> I'm experimenting with some Linux stuff right now and am currently working on something using epoll. But I've run into an issue where dmd just doesn't see anything in core.sys.linux.epoll. As a workaround, I've implemented my own declarations for the bits I'm using. I'm curious, though, if anyone else has encountered this as I've never seen anything like it. I get no errors at all about it not being able to find the module, just things like "epoll_event is undefined" and such. If I try something like this:
>
> import core.sys.linux.epoll : epoll_event;
>
> Then I get an error about the import not being found. Other modules in core.sys.linux import just fine.
>
> If anyone else can verify this same issue, I'll file a bug report. Otherwise, any ideas on what could cause this?

Odd.  I opened a pull request that fixed a case issue with the 'Linux'/'linux' version identifier in that module that I thought was accepted and merged.  Sounds like the same symptom.

https://github.com/D-Programming-Language/druntime/pull/489

September 11, 2013
On 9/11/2013 7:58 PM, goughy wrote:
>
> Odd.  I opened a pull request that fixed a case issue with the
> 'Linux'/'linux' version identifier in that module that I thought was
> accepted and merged.  Sounds like the same symptom.
>
> https://github.com/D-Programming-Language/druntime/pull/489
>

Yes, it's fixed in git master, but didn't make it into the current release. I stared at that epoll module for I don't know how long and never caught the Linux/linux thing. That potential problem was discussed around here more than once.