# 0.7 deprecation: Use \`at most one line break\`

**URL:** <https://discourse.julialang.org/t/0-7-deprecation-use-at-most-one-line-break/11663>\
**Category:** General Usage\
**Created:** [June 13, 2018, 9:30pm UTC](https://discourse.julialang.org/t/0-7-deprecation-use-at-most-one-line-break/11663 "2018-06-13T21:30:10Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)\
**Post date:** [June 13, 2018, 9:30pm UTC](https://discourse.julialang.org/t/0-7-deprecation-use-at-most-one-line-break/11663/1 "2018-06-13T21:30:10Z")

</div>

Hi, I’ve ported most of GMT.jl to 0.7 but keep receiving many of these. Don’t understand what it wants with this story of the line breaks.  
Thanks for pointers.

```julia
 Warning: Deprecated syntax `multiple line breaks between doc string and object` at C:\j\.julia\v0.7\GMT\src\gmtinfo.jl:53.
│ Use `at most one line break` instead.
└ @ nothing gmtinfo.jl:53

```

[https://github.com/GenericMappingTools/GMT.jl/blob/j07/src/gmtinfo.jl#L53](https://github.com/GenericMappingTools/GMT.jl/blob/j07/src/gmtinfo.jl#L53)

---

<div class="post-metadata">

**Author:** ![sdanisch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sdanisch/32/1406_2.png) [@sdanisch](https://discourse.julialang.org/u/sdanisch)\
**Post date:** [June 13, 2018, 9:33pm UTC](https://discourse.julialang.org/t/0-7-deprecation-use-at-most-one-line-break/11663/2 "2018-06-13T21:33:04Z")

</div>

You should remove the `# --------------` between docstring and `gmtinfo`!

---

<div class="post-metadata">

**Author:** ![chobbes](https://avatars.discourse-cdn.com/v4/letter/c/848f3c/32.png) [@chobbes](https://discourse.julialang.org/u/chobbes)\
**Post date:** [June 13, 2018, 9:48pm UTC](https://discourse.julialang.org/t/0-7-deprecation-use-at-most-one-line-break/11663/3 "2018-06-13T21:48:38Z")

</div>

Why is that line offending?

---

<div class="post-metadata">

**Author:** ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)\
**Post date:** [June 13, 2018, 11:40pm UTC](https://discourse.julialang.org/t/0-7-deprecation-use-at-most-one-line-break/11663/4 "2018-06-13T23:40:00Z")

</div>

Thanks. It worked, though I also wonder what’s offensive in having a comment line between doc string and the function declaration.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [June 13, 2018, 11:40pm UTC](https://discourse.julialang.org/t/0-7-deprecation-use-at-most-one-line-break/11663/5 "2018-06-13T23:40:40Z")

</div>

It might be better to require no blank lines between doc string and what it attaches to.

---

<div class="post-metadata">

**Author:** ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)\
**Post date:** [June 13, 2018, 11:43pm UTC](https://discourse.julialang.org/t/0-7-deprecation-use-at-most-one-line-break/11663/6 "2018-06-13T23:43:43Z")

</div>

> [@StefanKarpinski](#):
>
> blank lines between doc string and what it attaches to

It’s not a blank line. Any comment line will trigger that (so far) deprecation warning.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [June 14, 2018, 1:58am UTC](https://discourse.julialang.org/t/0-7-deprecation-use-at-most-one-line-break/11663/7 "2018-06-14T01:58:49Z")

</div>

Yes, what I’m saying is that only a blank line should trigger the warning, not a comment. So a doc string followed by however many lines that only have comments followed by an expression would behave as if the expression was on the next line after the doc string. But maybe that’s too complicated.

---

<div class="post-metadata">

**Author:** ![Per](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/per/32/10387_2.png) [@Per](https://discourse.julialang.org/u/Per)\
**Post date:** [June 14, 2018, 9:10am UTC](https://discourse.julialang.org/t/0-7-deprecation-use-at-most-one-line-break/11663/8 "2018-06-14T09:10:53Z")

</div>

I think it would be great if the parser would emit ignored-by-default `CommentNode`s in the same way that it currently emits `LineNumberNode`s. This would make it easy to identify comment lines as non-blank.

As a bonus it would become much easier to write utilities that take commands from comments in Julia code (e.g. to control how a document is linted or displayed).

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [June 14, 2018, 9:20am UTC](https://discourse.julialang.org/t/0-7-deprecation-use-at-most-one-line-break/11663/9 "2018-06-14T09:20:15Z")

</div>

See [https://github.com/ZacLN/CSTParser.jl](https://github.com/ZacLN/CSTParser.jl) which keeps everything in the AST enabling tools like [https://github.com/JuliaComputing/FemtoCleaner.jl](https://github.com/JuliaComputing/FemtoCleaner.jl) to be built on top of it.

---

<div class="post-metadata">

**Author:** ![Per](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/per/32/10387_2.png) [@Per](https://discourse.julialang.org/u/Per)\
**Post date:** [June 14, 2018, 9:21am UTC](https://discourse.julialang.org/t/0-7-deprecation-use-at-most-one-line-break/11663/10 "2018-06-14T09:21:30Z")

</div>

Looks great. Thanks!