|
00:14
MasterDuke left
08:03
dakkar joined
09:53
MasterDuke joined
10:19
wingfold joined
10:46
wingfold left
11:10
razetime joined
13:07
razetime left
13:38
razetime joined
13:46
Manifest0 left
13:47
Manifest0 joined
14:11
razetime left
14:55
razetime joined
15:38
razetime left
15:44
razetime joined
16:35
dakkar left
17:25
razetime left
18:37
zacts joined
18:49
zacts left
|
|||
| stevied | ok, I gotta think this is a bug: | 18:50 | |
| ``` | |||
| grammar HC2 { | |||
| token TOP { <line>+ } | |||
| token line { \N* \n } | |||
| } | |||
| ``` | |||
| otherwise, can someone explain why this does not match a file ending in with hex code `0a`, the newline character? | 18:51 | ||
| actually, I think it doesn' t end in 0a. | 18:56 | ||
| so that's gotta be the problem | |||
| actually, it does end in 0a on the disk | 18:58 | ||
| oh, holy crap. the comma ide is stripping it out | 19:01 | ||
| jesus | |||
| stackoverflow.com/a/71667703/1641112 | 19:21 | ||
| there's the answer | |||
|
19:23
n1to joined
19:59
zacts joined
20:40
discord-raku-bot left
20:41
discord-raku-bot joined
21:00
zacts left
|
|||
| Anton Antonov | @stevied#8273 I having similar frustrations using this package: github.com/antononcube/Raku-Gramma...Processing . It parses Raku files just fine inside Comma, but not on the command line! | 21:12 | |
| stevied | this stuff can get frustrating for sure. I just spend ridiculous amounts of time on it until I figure it out | 21:16 | |
| Anton Antonov | Thanks for figuring that out! | 21:17 | |
|
21:24
zacts joined
|
|||
| stevied | grammars are still driving me crazy. Just when I think I have them figured it it looks like I've made another bad assumption about how they process the text. | 21:28 | |
| like i'm finding out that apparently you can't do a negative lookahead assertion in a token | 21:30 | ||
| i don't know. that may not be true. but my grammar isn't working for some weird reason | 21:32 | ||
| this has got to be a bug or i'm just a total idiot. | 21:38 | ||
| in my defense, this stuff isn''t easy | 21:39 | ||
|
21:45
zacts left
|
|||
| Anton Antonov | Yes, there are some very hard to figure out or navigate points. BTW, some of the things you trying to do might have been figured out by DrForr (github.com/drforr). | 21:49 | |
| stevied | stackoverflow.com/questions/716691...-assertion | 21:51 | |
|
21:51
n1to left
|
|||
| yeah, i realize i'm probably reinventing the wheel. but my primary goal is to learn raku. so I'm working in a problem space I'm familiar with to help do that. | 21:53 | ||
| Anton Antonov | Same here -- I pointed out that repository as source code look-up place. Not as package, en-bloc replacement of what you od. | ||
| Same here -- I pointed out that repository as source code look-up place. Not as package, en-bloc replacement of what you do. | |||
| Same here -- I pointed out that repository as a source code look-up place. Not as package, en-bloc replacement of what you do. | 21:54 | ||
| Same here -- I pointed out that repository as a source code look-up place. Not as a package, en-bloc replacement of what you do. | 21:55 | ||
| Nemokosch | is that really a lookahead, not just usual negative matching? | ||
| and where is <header-content>? | 21:57 | ||
| stevied | crap, did i cut that off | 22:03 | |
| let me add | |||
| fixed | 22:04 | ||
| it's called a "lookaround assertion" | |||
| docs.raku.org/language/regexes#Loo...assertions | 22:05 | ||
| maybe they behave differently than lookahead? if they do, I don't get it | 22:06 | ||
| i think the heading sizes in the docs are wrong | 22:07 | ||
| i think lookahead and lookbehind are types of "lookaround". doc outline level doesn't reflect that, though | |||
|
22:58
destroycomputers joined
23:08
zacts joined
|
|||
| ok, did some more searching: stackoverflow.com/questions/626860...ar-in-raku | 23:34 | ||
| same question. not a bug, but it doesn't work as expected | |||