Tickets :: Comment on [#7963] Horde's Yaml parser chokes on legal tabs.

Search Results: 14 of 248 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: .___.__. __..__ . [__ \| \|(__ [__)\| \| \|__\|.__)[__)\|___
Comment	> The following code snipped demonstrates that Horde's Yaml parser > chokes on legal (non-indentation) tabs in Yaml content. The snippet > is also attached to this ticket. > > > > Spyc and Syck have the same bug. (sfYaml does not, but it has other bugs.) > > > > Thanks! > > > > <?php > > > > > > $yaml0 = "- [ one, two ]\n"; // separated by 2 tabs > > $yaml1 = "- [ one, two ]\n"; // separated by 2 spaces > > > > > > require_once ("Horde/Yaml.php"); > > require_once ("Horde/Yaml/Dumper.php"); > > require_once ("Horde/Yaml/Exception.php"); > > require_once ("Horde/Yaml/Loader.php"); > > require_once ("Horde/Yaml/Node.php"); > > > > > > print_r (Horde_Yaml::load ($yaml0)); > > print_r (Horde_Yaml::load ($yaml1)); > > > > > > /* > ---------------------------------------------------------------------------- > > > > I expect identical output, but I get this: > > > > Array > > ( > > [0] => Array > > ( > > [0] => one, two > > ) > > > > ) > > Array > > ( > > [0] => Array > > ( > > [0] => one > > [1] => two > > ) > > > > ) > > > > ---------------------------------------------------------------------------- > */ > > > > > > ?> > >
Attachment
Watch this ticket