public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "development at efficientek dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29931] New: Comments should not respect line continuation
Date: Thu, 22 Dec 2022 04:41:12 +0000	[thread overview]
Message-ID: <bug-29931-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29931

            Bug ID: 29931
           Summary: Comments should not respect line continuation
           Product: gdb
           Version: 12.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: development at efficientek dot com
  Target Milestone: ---

The following script does nothing (in 12.1), but I think most end-users would
find this unexpected (as do I).

# === begin ===

# with set width 0 -- \
printf "This does not execute"

# === end ===

Its expected that nothing in the line of a comment can affect the running of
the script. Respecting line continuations violates this. This is unlike bash,
sh, and python scripts, which also use '#' as comments and which do not respect
line continuations in comments.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-12-22  4:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22  4:41 development at efficientek dot com [this message]
2022-12-22 14:59 ` [Bug gdb/29931] " schwab@linux-m68k.org
2022-12-22 16:36 ` development at efficientek dot com
2022-12-22 16:47 ` development at efficientek dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29931-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).