我想解析(首先,只识别,保留符号)LaTeX 数学。现在,我遇到了 super 和下标的问题,结合花括号(例如 a^{bc} 及其组合,我有基本的 a^b 工作正常)。一个最小的例子(尽可能短,同时保持可读性):
#include <iostream>
using std::cout;
#include <string>
using std::string;
#include <boost/spirit/home/x3.hpp>
namespace x3 = boost::spirit::x3;
using x3::space;
using x3::char_;
using x3::lit;
using x3::repeat;
x3::rule<struct scripts, string> scripts = "super- and subscripts";
x3::rule<struct braced_thing, string> braced_thing = "thing optionaly surrounded by curly braces";
x3::rule<struct superscript, string> superscript = "superscript";
x3::rule<struct subscript, string> subscript = "subscript";
// main rule: any number of items with or without braces
auto const scripts_def = *braced_thing;
// second level main rule: optional braces, and any number of characters or sub/superscripts
auto const braced_thing_def = -lit('{') >> *(subscript | superscript | repeat(1)[(char_ - "_^{}")]) >> -lit('}');
// superscript: things of the form a^b where a and b can be surrounded by curly braces
auto const superscript_def = braced_thing >> '^' >> braced_thing;
// subscript: things of the form a_b where a and b can be surrounded by curly braces
auto const subscript_def = braced_thing >> '_' >> braced_thing;
BOOST_SPIRIT_DEFINE(scripts)
BOOST_SPIRIT_DEFINE(braced_thing)
BOOST_SPIRIT_DEFINE(superscript)
BOOST_SPIRIT_DEFINE(subscript)
int main()
{
const string input = "a^{b_x y}_z {v_x}^{{x^z}_y}";
string output; // will only contain the characters as the grammar is defined above
auto first = input.begin();
auto last = input.end();
const bool result = x3::phrase_parse(first, last,
scripts,
space,
output);
if(first != last)
std::cout << "partial match only:\n" << output << '\n';
else if(!result)
std::cout << "parse failed!\n";
else
std::cout << "parsing succeeded:\n" << output << '\n';
}
它也是 Available on Coliru 。
问题是,这个段错误(我确信原因很明显)而且我没有其他方式,好吧,用...表达式语法来表达它。
最佳答案
我还没有看过@cv_and_he 的建议,而是自己实时调试你的语法。我想到了这个:
auto token = lexeme [ +~char_("_^{} \t\r\n") ];
auto simple = '{' >> sequence >> '}' | token;
auto expr = lexeme [ simple % char_("_^") ];
auto sequence_def = expr % +space;
让我走到这一步的基本上是对实际语法的逐步重新思考/想象。
It took me two tries to think of the right way to get
"a b"parsing (at first I "hacked" it a just another subscript operator inchar_(" _^")but I got the impression that would not lead to an AST as you expect it. The clue being you used a skipper for the space).
现在,没有 AST,但我们只是“收获”了使用.. x3::raw[...] 匹配的原始字符串。
//#define BOOST_SPIRIT_X3_DEBUG
#include <iostream>
#include <string>
#include <boost/spirit/home/x3.hpp>
namespace x3 = boost::spirit::x3;
namespace grammar {
using namespace x3;
rule<struct _s> sequence { "sequence" };
auto simple = rule<struct _s> {"simple"} = '{' >> sequence >> '}' | lexeme [ +~char_("_^{} \t\r\n") ];
auto expr = rule<struct _e> {"expr"} = lexeme [ simple % char_("_^") ];
auto sequence_def = expr % +space;
BOOST_SPIRIT_DEFINE(sequence)
}
int main() {
for (const std::string input : {
"a",
"a^b", "a_b", "a b",
"{a}^{b}", "{a}_{b}", "{a} {b}",
"a^{b_x y}",
"a^{b_x y}_z {v_x}^{{x^z}_y}"
})
{
std::string output; // will only contain the characters as the grammar is defined above
auto first = input.begin(), last = input.end();
bool result = x3::parse(first, last, x3::raw[grammar::sequence], output);
if (result)
std::cout << "Parse success: '" << output << "'\n";
else
std::cout << "parse failed!\n";
if (last!=first)
std::cout << "remaining unparsed: '" << std::string(first, last) << "'\n";
}
}
输出:
Parse success: 'a'
Parse success: 'a^b'
Parse success: 'a_b'
Parse success: 'a b'
Parse success: '{a}^{b}'
Parse success: '{a}_{b}'
Parse success: '{a} {b}'
Parse success: 'a^{b_x y}'
Parse success: 'a^{b_x y}_z {v_x}^{{x^z}_y}'
启用调试信息的输出:
<sequence>
<try>a</try>
<expr>
<try>a</try>
<simple>
<try>a</try>
<success></success>
</simple>
<success></success>
</expr>
<success></success>
</sequence>
Parse success: 'a'
<sequence>
<try>a^b</try>
<expr>
<try>a^b</try>
<simple>
<try>a^b</try>
<success>^b</success>
</simple>
<simple>
<try>b</try>
<success></success>
</simple>
<success></success>
</expr>
<success></success>
</sequence>
Parse success: 'a^b'
<sequence>
<try>a_b</try>
<expr>
<try>a_b</try>
<simple>
<try>a_b</try>
<success>_b</success>
</simple>
<simple>
<try>b</try>
<success></success>
</simple>
<success></success>
</expr>
<success></success>
</sequence>
Parse success: 'a_b'
<sequence>
<try>a b</try>
<expr>
<try>a b</try>
<simple>
<try>a b</try>
<success> b</success>
</simple>
<success> b</success>
</expr>
<expr>
<try>b</try>
<simple>
<try>b</try>
<success></success>
</simple>
<success></success>
</expr>
<success></success>
</sequence>
Parse success: 'a b'
<sequence>
<try>{a}^{b}</try>
<expr>
<try>{a}^{b}</try>
<simple>
<try>{a}^{b}</try>
<sequence>
<try>a}^{b}</try>
<expr>
<try>a}^{b}</try>
<simple>
<try>a}^{b}</try>
<success>}^{b}</success>
</simple>
<success>}^{b}</success>
</expr>
<success>}^{b}</success>
</sequence>
<success>^{b}</success>
</simple>
<simple>
<try>{b}</try>
<sequence>
<try>b}</try>
<expr>
<try>b}</try>
<simple>
<try>b}</try>
<success>}</success>
</simple>
<success>}</success>
</expr>
<success>}</success>
</sequence>
<success></success>
</simple>
<success></success>
</expr>
<success></success>
</sequence>
Parse success: '{a}^{b}'
<sequence>
<try>{a}_{b}</try>
<expr>
<try>{a}_{b}</try>
<simple>
<try>{a}_{b}</try>
<sequence>
<try>a}_{b}</try>
<expr>
<try>a}_{b}</try>
<simple>
<try>a}_{b}</try>
<success>}_{b}</success>
</simple>
<success>}_{b}</success>
</expr>
<success>}_{b}</success>
</sequence>
<success>_{b}</success>
</simple>
<simple>
<try>{b}</try>
<sequence>
<try>b}</try>
<expr>
<try>b}</try>
<simple>
<try>b}</try>
<success>}</success>
</simple>
<success>}</success>
</expr>
<success>}</success>
</sequence>
<success></success>
</simple>
<success></success>
</expr>
<success></success>
</sequence>
Parse success: '{a}_{b}'
<sequence>
<try>{a} {b}</try>
<expr>
<try>{a} {b}</try>
<simple>
<try>{a} {b}</try>
<sequence>
<try>a} {b}</try>
<expr>
<try>a} {b}</try>
<simple>
<try>a} {b}</try>
<success>} {b}</success>
</simple>
<success>} {b}</success>
</expr>
<success>} {b}</success>
</sequence>
<success> {b}</success>
</simple>
<success> {b}</success>
</expr>
<expr>
<try>{b}</try>
<simple>
<try>{b}</try>
<sequence>
<try>b}</try>
<expr>
<try>b}</try>
<simple>
<try>b}</try>
<success>}</success>
</simple>
<success>}</success>
</expr>
<success>}</success>
</sequence>
<success></success>
</simple>
<success></success>
</expr>
<success></success>
</sequence>
Parse success: '{a} {b}'
<sequence>
<try>a^{b_x y}</try>
<expr>
<try>a^{b_x y}</try>
<simple>
<try>a^{b_x y}</try>
<success>^{b_x y}</success>
</simple>
<simple>
<try>{b_x y}</try>
<sequence>
<try>b_x y}</try>
<expr>
<try>b_x y}</try>
<simple>
<try>b_x y}</try>
<success>_x y}</success>
</simple>
<simple>
<try>x y}</try>
<success> y}</success>
</simple>
<success> y}</success>
</expr>
<expr>
<try>y}</try>
<simple>
<try>y}</try>
<success>}</success>
</simple>
<success>}</success>
</expr>
<success>}</success>
</sequence>
<success></success>
</simple>
<success></success>
</expr>
<success></success>
</sequence>
Parse success: 'a^{b_x y}'
<sequence>
<try>a^{b_x y}_z {v_x}^{{</try>
<expr>
<try>a^{b_x y}_z {v_x}^{{</try>
<simple>
<try>a^{b_x y}_z {v_x}^{{</try>
<success>^{b_x y}_z {v_x}^{{x</success>
</simple>
<simple>
<try>{b_x y}_z {v_x}^{{x^</try>
<sequence>
<try>b_x y}_z {v_x}^{{x^z</try>
<expr>
<try>b_x y}_z {v_x}^{{x^z</try>
<simple>
<try>b_x y}_z {v_x}^{{x^z</try>
<success>_x y}_z {v_x}^{{x^z}</success>
</simple>
<simple>
<try>x y}_z {v_x}^{{x^z}_</try>
<success> y}_z {v_x}^{{x^z}_y</success>
</simple>
<success> y}_z {v_x}^{{x^z}_y</success>
</expr>
<expr>
<try>y}_z {v_x}^{{x^z}_y}</try>
<simple>
<try>y}_z {v_x}^{{x^z}_y}</try>
<success>}_z {v_x}^{{x^z}_y}</success>
</simple>
<success>}_z {v_x}^{{x^z}_y}</success>
</expr>
<success>}_z {v_x}^{{x^z}_y}</success>
</sequence>
<success>_z {v_x}^{{x^z}_y}</success>
</simple>
<simple>
<try>z {v_x}^{{x^z}_y}</try>
<success> {v_x}^{{x^z}_y}</success>
</simple>
<success> {v_x}^{{x^z}_y}</success>
</expr>
<expr>
<try>{v_x}^{{x^z}_y}</try>
<simple>
<try>{v_x}^{{x^z}_y}</try>
<sequence>
<try>v_x}^{{x^z}_y}</try>
<expr>
<try>v_x}^{{x^z}_y}</try>
<simple>
<try>v_x}^{{x^z}_y}</try>
<success>_x}^{{x^z}_y}</success>
</simple>
<simple>
<try>x}^{{x^z}_y}</try>
<success>}^{{x^z}_y}</success>
</simple>
<success>}^{{x^z}_y}</success>
</expr>
<success>}^{{x^z}_y}</success>
</sequence>
<success>^{{x^z}_y}</success>
</simple>
<simple>
<try>{{x^z}_y}</try>
<sequence>
<try>{x^z}_y}</try>
<expr>
<try>{x^z}_y}</try>
<simple>
<try>{x^z}_y}</try>
<sequence>
<try>x^z}_y}</try>
<expr>
<try>x^z}_y}</try>
<simple>
<try>x^z}_y}</try>
<success>^z}_y}</success>
</simple>
<simple>
<try>z}_y}</try>
<success>}_y}</success>
</simple>
<success>}_y}</success>
</expr>
<success>}_y}</success>
</sequence>
<success>_y}</success>
</simple>
<simple>
<try>y}</try>
<success>}</success>
</simple>
<success>}</success>
</expr>
<success>}</success>
</sequence>
<success></success>
</simple>
<success></success>
</expr>
<success></success>
</sequence>
Parse success: 'a^{b_x y}_z {v_x}^{{x^z}_y}'
关于c++ - 我如何让这个递归规则起作用?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/34514784/
我正在学习如何使用Nokogiri,根据这段代码我遇到了一些问题:require'rubygems'require'mechanize'post_agent=WWW::Mechanize.newpost_page=post_agent.get('http://www.vbulletin.org/forum/showthread.php?t=230708')puts"\nabsolutepathwithtbodygivesnil"putspost_page.parser.xpath('/html/body/div/div/div/div/div/table/tbody/tr/td/div
总的来说,我对ruby还比较陌生,我正在为我正在创建的对象编写一些rspec测试用例。许多测试用例都非常基础,我只是想确保正确填充和返回值。我想知道是否有办法使用循环结构来执行此操作。不必为我要测试的每个方法都设置一个assertEquals。例如:describeitem,"TestingtheItem"doit"willhaveanullvaluetostart"doitem=Item.new#HereIcoulddotheitem.name.shouldbe_nil#thenIcoulddoitem.category.shouldbe_nilendend但我想要一些方法来使用
关闭。这个问题是opinion-based.它目前不接受答案。想要改进这个问题?更新问题,以便editingthispost可以用事实和引用来回答它.关闭4年前。Improvethisquestion我想在固定时间创建一系列低音和高音调的哔哔声。例如:在150毫秒时发出高音调的蜂鸣声在151毫秒时发出低音调的蜂鸣声200毫秒时发出低音调的蜂鸣声250毫秒的高音调蜂鸣声有没有办法在Ruby或Python中做到这一点?我真的不在乎输出编码是什么(.wav、.mp3、.ogg等等),但我确实想创建一个输出文件。
给定这段代码defcreate@upgrades=User.update_all(["role=?","upgraded"],:id=>params[:upgrade])redirect_toadmin_upgrades_path,:notice=>"Successfullyupgradeduser."end我如何在该操作中实际验证它们是否已保存或未重定向到适当的页面和消息? 最佳答案 在Rails3中,update_all不返回任何有意义的信息,除了已更新的记录数(这可能取决于您的DBMS是否返回该信息)。http://ar.ru
我在我的项目目录中完成了compasscreate.和compassinitrails。几个问题:我已将我的.sass文件放在public/stylesheets中。这是放置它们的正确位置吗?当我运行compasswatch时,它不会自动编译这些.sass文件。我必须手动指定文件:compasswatchpublic/stylesheets/myfile.sass等。如何让它自动运行?文件ie.css、print.css和screen.css已放在stylesheets/compiled。如何在编译后不让它们重新出现的情况下删除它们?我自己编译的.sass文件编译成compiled/t
我正在寻找执行以下操作的正确语法(在Perl、Shell或Ruby中):#variabletoaccessthedatalinesappendedasafileEND_OF_SCRIPT_MARKERrawdatastartshereanditcontinues. 最佳答案 Perl用__DATA__做这个:#!/usr/bin/perlusestrict;usewarnings;while(){print;}__DATA__Texttoprintgoeshere 关于ruby-如何将脚
Rackup通过Rack的默认处理程序成功运行任何Rack应用程序。例如:classRackAppdefcall(environment)['200',{'Content-Type'=>'text/html'},["Helloworld"]]endendrunRackApp.new但是当最后一行更改为使用Rack的内置CGI处理程序时,rackup给出“NoMethodErrorat/undefinedmethod`call'fornil:NilClass”:Rack::Handler::CGI.runRackApp.newRack的其他内置处理程序也提出了同样的反对意见。例如Rack
在选择我想要运行操作的频率时,唯一的选项是“每天”、“每小时”和“每10分钟”。谢谢!我想为我的Rails3.1应用程序运行调度程序。 最佳答案 这不是一个优雅的解决方案,但您可以安排它每天运行,并在实际开始工作之前检查日期是否为当月的第一天。 关于ruby-如何每月在Heroku运行一次Scheduler插件?,我们在StackOverflow上找到一个类似的问题: https://stackoverflow.com/questions/8692687/
我有一个对象has_many应呈现为xml的子对象。这不是问题。我的问题是我创建了一个Hash包含此数据,就像解析器需要它一样。但是rails自动将整个文件包含在.........我需要摆脱type="array"和我该如何处理?我没有在文档中找到任何内容。 最佳答案 我遇到了同样的问题;这是我的XML:我在用这个:entries.to_xml将散列数据转换为XML,但这会将条目的数据包装到中所以我修改了:entries.to_xml(root:"Contacts")但这仍然将转换后的XML包装在“联系人”中,将我的XML代码修改为
我有一大串格式化数据(例如JSON),我想使用Psychinruby同时保留格式转储到YAML。基本上,我希望JSON使用literalstyle出现在YAML中:---json:|{"page":1,"results":["item","another"],"total_pages":0}但是,当我使用YAML.dump时,它不使用文字样式。我得到这样的东西:---json:!"{\n\"page\":1,\n\"results\":[\n\"item\",\"another\"\n],\n\"total_pages\":0\n}\n"我如何告诉Psych以想要的样式转储标量?解