| Server IP : 101.53.144.229 / Your IP : 216.73.216.181 Web Server : Apache System : Linux host.gdigitalindia.in 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 User : digitalshiksha ( 1179) PHP Version : 5.6.40 Disable Function : eval,show_source,system,shell_exec,escapeshellarg,escapeshellcmd,proc_close,proc_open,ini_alter,dl,show_source,curl_multi_exechellcmd, ini_restore,apache_get_modules,get_cfg_var,passthru, exec ,proc_get_status,fpassthru,c999_buff_prepare,c999_sess_put,c99_buff_prepare,c99_sess_put,proc_close,ini_alter,dl,symlink,link,proc_close,ini_alter,dl,symlink,link,mail MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/perl-YAML-Syck-1.27/ |
Upload File : |
YAML::Syck and YAML.pm 0.60 breaks compatibility with older versions by
changing the tags that are output for serialized objects.
This was the old way:
--- !perl/Foo::Bar {}
--- !perl/@Baz []
--- !perl/$Quux ""
New way:
--- !!perl/hash:Foo::Bar {}
--- !!perl/array:Baz []
--- !!perl/scalar:Quux ""
* This change was made after discussions with the Python and Ruby
implementers to standardize on this form.
* YAML::Syck was updated at the same time as YAML.pm so that they
serialize objects the same way.
* YAML.pm roundtrips the new format and still parses the old (now
deprecated) format.
* The best strategy is to update to the latest version.
* There are potential problems if you use YAML for RPC and the server
and client versions don't match.