From: John P. <jpe...@ro...> - 2006-02-15 19:11:29
Attachments:
yaml_version
|
Dear Perl YAML-heads: I've been trying to integrate version objects into Module::Build (now that I have a pure Perl release) and everything works except that YAML emits lots of warnings when trying to dump version objects: Use of uninitialized value in hash element at /usr/lib/perl5/site_perl/5.8.7/YAML.pm line 283. Use of uninitialized value in string eq at /usr/lib/perl5/site_perl/5.8.7/YAML.pm line 291. ...blah...blah...blah... --- !perl/YAML::Warning code: YAML_DUMP_WARN_BAD_NODE_TYPE msg: "Can't perform serialization for node type " ... I've tried to implement a yaml_dump() sub in the class, but I cannot figure out how to use it (the commented out Bless line just croaks). I've attached my example code (which requires version). TIA John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 |
From: John P. <jpe...@ro...> - 2006-02-15 22:05:54
|
John Peacock wrote: > Dear Perl YAML-heads: > > I've been trying to integrate version objects into Module::Build (now > that I have a pure Perl release) and everything works except that YAML > emits lots of warnings when trying to dump version objects: Never mind. Upgrading YAML to current (0.58) works much better and setting $YAML::Stringify does exactly what we want. John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 |
From: Ken W. <ke...@ma...> - 2006-02-16 15:35:36
|
On Feb 15, 2006, at 4:06 PM, John Peacock wrote: > John Peacock wrote: >> Dear Perl YAML-heads: >> I've been trying to integrate version objects into Module::Build (now >> that I have a pure Perl release) and everything works except that >> YAML emits lots of warnings when trying to dump version objects: > > Never mind. Upgrading YAML to current (0.58) works much better and > setting $YAML::Stringify does exactly what we want. Is there no way to support YAML 0.35? That's our current YAML prerequisite. -Ken |
From: John P. <jpe...@ro...> - 2006-02-16 17:46:21
|
Ken Williams wrote: > > On Feb 15, 2006, at 4:06 PM, John Peacock wrote: >> Never mind. Upgrading YAML to current (0.58) works much better and >> setting $YAML::Stringify does exactly what we want. > > Is there no way to support YAML 0.35? That's our current YAML > prerequisite. Nope. Once you throw an object into the mix, YAML gets very confused. Apply my patch and try it with 0.35 and you will see: 1) a screenful of warnings thrown during the META.yml creation; 2) worse yet, the META.yml is malformed (it doesn't include either a dump of the version object as hash nor the correct stringified representation). I can, with some more difficulty, patch M::B to force a stringification of version objects prior to inserting them into the $node, but it isn't nearly as clean. Is there some overriding reason you are avoiding upgrading the YAML prereq to 0.50 (which in itself isn't even the current rev)? John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 |
From: Ken W. <ke...@ma...> - 2006-02-16 17:55:48
|
On Feb 16, 2006, at 11:46 AM, John Peacock wrote: > Is there some overriding reason you are avoiding upgrading the YAML > prereq to 0.50 (which in itself isn't even the current rev)? Good question. I guess not, though this is the first time I think we'd upgrade an auto-feature dependency, and it has just occurred to me that it'll catch people by surprise if they currently have that feature enabled. It will suddenly get non-enabled without much warning. -Ken |
From: <in...@tt...> - 2006-02-16 19:50:49
|
Ken, You definitely want to use 0.58+ for your prereqs. For a couple of 0.5x releases there were Spiffy deps etc, but that's all been resolved. Now YAML.pm requires no extra deps. Also with 0.58 I can fix bugs and turn around releases in short order (well depending on the bug ;) Cheers, Ingy On 16/02/06 11:55 -0600, Ken Williams wrote: > > On Feb 16, 2006, at 11:46 AM, John Peacock wrote: > > >Is there some overriding reason you are avoiding upgrading the YAML > >prereq to 0.50 (which in itself isn't even the current rev)? > > Good question. I guess not, though this is the first time I think we'd > upgrade an auto-feature dependency, and it has just occurred to me that > it'll catch people by surprise if they currently have that feature > enabled. It will suddenly get non-enabled without much warning. > > -Ken > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Yaml-core mailing list > Yam...@li... > https://lists.sourceforge.net/lists/listinfo/yaml-core |
From: Ingy d. N. <in...@tt...> - 2006-02-18 03:28:44
|
On 17/02/06 01:51 -0800, Yitzchak Scott-Thoennes wrote: > On Thu, Feb 16, 2006 at 12:03:18PM -0800, Ingy dot Net wrote: > > Ken, > > > > You definitely want to use 0.58+ for your prereqs. > > > > For a couple of 0.5x releases there were Spiffy deps etc, but that's all been > > resolved. Now YAML.pm requires no extra deps. > > You realize that you still have build_requires Test::Base 0.49 > and Test-Base requires Spiffy? These are bundled as testing artifacts. You need neither installed on your machine and the YAML dist installs neither. Try installing YAML on a clean Perl. :) Cheers, Ingy |
From: Ingy d. N. <in...@tt...> - 2006-02-18 08:20:50
|
On 17/02/06 21:52 -0600, Ken Williams wrote: > > On Feb 17, 2006, at 9:42 PM, Ingy dot Net wrote: > > >On 17/02/06 01:51 -0800, Yitzchak Scott-Thoennes wrote: > >>On Thu, Feb 16, 2006 at 12:03:18PM -0800, Ingy dot Net wrote: > >>>Ken, > >>> > >>>You definitely want to use 0.58+ for your prereqs. > >>> > >>>For a couple of 0.5x releases there were Spiffy deps etc, but that's > >>>all been > >>>resolved. Now YAML.pm requires no extra deps. > >> > >>You realize that you still have build_requires Test::Base 0.49 > >>and Test-Base requires Spiffy? > > > >These are bundled as testing artifacts. You need neither installed on > >your > >machine and the YAML dist installs neither. > > It needs to be removed from build_requires, then, because when it's in > there, installation tools will think they need to fetch & install it. > > -Ken You mean in the META.yml? Module::Install generates that for me. Is it wrong? Cheers, Ingy |