Perl 6 - the future is here, just unevenly distributed

IRC log for #inline, 2015-08-14

| Channels | #inline index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:13 willthechill joined #inline
03:33 [1]mohawk joined #inline
03:39 davido_ joined #inline
04:12 willthechill okay I have found a super-annoying error in Inline, if there are a large number of commented-out lines in your C/C++ source file, you will get very mysterious errors of "subroutine foo() not declared in this scope" even though the subroutine is just fine
04:12 willthechill deleting the comments causes it to work!
04:12 willthechill this is very much not good
04:13 willthechill davido_: you around?
04:19 davido_ i'm around
04:19 davido_ If it's happening both with C and C++, it's not Inline::CPP specific, right?
04:32 davido___ joined #inline
04:37 davido_ joined #inline
04:52 willthechill I'm not sure yet
04:52 willthechill I'm remembering now I've experienced this before
04:59 willthechill so I never filed a bug report for this, but I did experience it before
04:59 willthechill the reason I didn't report it was that I could not come up with a simple test case
04:59 willthechill I currently have a complex test case
05:00 willthechill it happens while I'm debugging my code, and commenting-out huge portions of it in C++, using both // and /* */
05:01 willthechill the C++ code seems to compile correctly except for an Inline-generated code error along the lines of "XS_main_foo(): error, foo() was not declared in this scope"
05:01 willthechill where obviously foo WAS declared in this scope, and once I delete the comment blocks it works
05:02 willthechill I'm not sure how the XS subroutine naming convention works, but if XS_main_foo() means foo() is in the main:: namespace, then that part is wrong because foo() is a class method in some namespace other than main::
05:02 willthechill so maybe the class/namespace parsing part breaks if it encounters too many comments?
05:05 willthechill I can't spend the time right now to try and come up with a simpler test case, shall I still file a bug report?  I don't know which repo to file under...
06:17 willthechill okay there may be another different bug, or perhaps the same bug in different (confusing) form...  std::array does not work with Inline::CPP and gives the same error as mentioned above
06:17 willthechill so I think it IS Inline::CPP specific
06:18 willthechill whereas std::vector works just fine
06:22 willthechill is there some reason why std::array doesn't work as a member variable in a C++ class via Inline::CPP?
06:47 rurban joined #inline
07:48 mohawk willthechill, it might be a comments-parsing bug
07:48 mohawk make a github issue with a repro case and we'll take a look at it
10:34 rurban joined #inline
12:12 rurban joined #inline
12:51 rurban joined #inline
13:12 rurban left #inline
13:16 rurban joined #inline
13:29 davido__ joined #inline
13:33 rurban left #inline
15:02 leont joined #inline
18:13 willthechill mohawk: okay
18:14 willthechill is there any reason why std::array would not work as a member variable in a class?
18:45 leont It'd be a bit unusual, but I think it should work
18:45 leont (or did I miss some context)
18:50 stephen joined #inline
19:13 rurban joined #inline
20:29 rurban joined #inline

| Channels | #inline index | Today | | Search | Google Search | Plain-Text | summary