Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extra newline after empty arrays/hashes [rt.cpan.org #38554] #36

Open
toddr opened this issue May 11, 2017 · 0 comments
Open

Extra newline after empty arrays/hashes [rt.cpan.org #38554] #36

toddr opened this issue May 11, 2017 · 0 comments

Comments

@toddr
Copy link
Member

toddr commented May 11, 2017

Migrated from rt.cpan.org#38554 (status was 'stalled')

Requestors:

From srezic@cpan.org on 2008-08-18 08:39:23:

YAML::Syck emits extra newlines after empty array or hash references.
While this is not an error, the output looks somewhat aesthetically
unpleasant.

Regards,
    Slaven

From avar@cpan.org on 2010-05-20 11:24:36:

On Mon Aug 18 04:39:23 2008, SREZIC wrote:
> YAML::Syck emits extra newlines after empty array or hash references.
> While this is not an error, the output looks somewhat aesthetically
> unpleasant.

Patches / tests welcome!

(This is a form-reply that isn't specific to your particular report)

YAML::Syck has just acquired one new maintainer (me), it still doesn't
have anyone that *cares* about it. But I'm willing to help solve your
report & release a new version with the fix if it's easy for me.

It now has a Git repository at:

    http://github.com/avar/YAML-Syck

If your report is a patch that fixes a problem, great. Please remake
the patch against Git by forking that repo and sending me a pull
request on GitHub (or an update to this bug if you prefer
git-format-patch(1) or some other repo provider..). Make sure to
include a test for what you fixed.

If your report is some code that fails (and you have a testcase for
it) a patch against the test suite to demonstrate that failure would
be very useful. It's OK if the test crashes and burns, see
Test::More's docs for how to make TODO tests that fail now, but
shouldn't. Even if it segfaults perl C<system $^X => qw/ -Mblib
-MYAML::Syck .../> or something like that and checking the return
value will do.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant