Skip to content
New issue

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

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

Already on GitHub? # to your account

Change file ending from .som to .ns #181

Merged
merged 2 commits into from
Aug 7, 2017
Merged

Change file ending from .som to .ns #181

merged 2 commits into from
Aug 7, 2017

Conversation

smarr
Copy link
Owner

@smarr smarr commented Aug 5, 2017

With the recent improvements to the parser, we have a reasonable high level of spec compliance.
So, I think it would be appropriate to change the file ending from .som to .ns to reflect it.

This PR solves #180.

@smarr smarr added enhancement Improves the implementation with something noteworthy language-design Not everything is in the spec, sometimes, we need to decide what's best. labels Aug 5, 2017
@smarr smarr added this to the v0.5.0 - More Newspeak milestone Aug 5, 2017
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 80.028% when pulling 71c931f on ns-file-names into d9cb2dc on dev.

smarr added 2 commits August 7, 2017 11:47
Signed-off-by: Stefan Marr <git@stefan-marr.de>
Signed-off-by: Stefan Marr <git@stefan-marr.de>
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 880db29 on ns-file-names into ** on dev**.

@smarr smarr merged commit 40f5920 into dev Aug 7, 2017
@smarr smarr deleted the ns-file-names branch August 7, 2017 10:02
@smarr smarr mentioned this pull request Aug 7, 2017
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement Improves the implementation with something noteworthy language-design Not everything is in the spec, sometimes, we need to decide what's best.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants