From: Greg.mpls@... Date: 2019-06-16T13:48:17+00:00 Subject: [ruby-core:93183] [Ruby trunk Bug#15924] Ripper::Lexer RuntimeError - Ripper FATAL - master/trunk Issue #15924 has been updated by MSP-Greg (Greg L). @nobu Thanks. Actually, YARD doesn't use the Lexer, but I switched to using it a long time ago, and all the repos shown at https://msp-greg.github.io/ are created using it. Conversely, Lexer is subclassed from parser. So what's using what is a little vague... Until recently, all code snippets have flipped Ripper#error? to true. I guess it is a edge case. Ok to close... ---------------------------------------- Bug #15924: Ripper::Lexer RuntimeError - Ripper FATAL - master/trunk https://bugs.ruby-lang.org/issues/15924#change-78624 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.7.0dev (2019-06-15T03:04:16Z master 5d79054906) [x64-mingw32] * Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN ---------------------------------------- YARD based docs systems use Ripper for highlighting both source code and 'code snippets' in comments and rdoc/md files. Using the build shown, I have an error as shown: ``` lib/ruby/2.7.0/ripper/lexer.rb:101:in `lex' lib/ruby/2.7.0/ripper/lexer.rb:123:in `parse' lib/ruby/2.7.0/ripper/lexer.rb:123:in `parse': [Ripper FATAL] unknown token -1 (RuntimeError) ``` A quick look shows that it was parsing the rdoc files in the doc folder. Sorry for not being able to check further tonite, I'll look more tomorrow... -- https://bugs.ruby-lang.org/ Unsubscribe: