zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: c++ comments
Date: Wed, 22 Oct 2014 21:41:20 -0700	[thread overview]
Message-ID: <141022214120.ZM18075@torch.brasslantern.com> (raw)
In-Reply-To: <54486EE9.8060101@eastlink.ca>

On Oct 22,  7:58pm, Ray Andrews wrote:
}
} How can I legalize c++ comments? Or would that be a deep blasphemy?

Zsh historically has been built with compilers that do not support c++
comment syntax.  I'm not rabidly opposed to it, but tend to think we
should continue to avoid it in the zsh sources.

The foregoing assumes I correctly understand what "legalize" means to
you, and that the zsh sources are in fact what you're talking about.

} As it is, well nuts, you'd think it would give me a msg: "No c++
} comments permitted, sinner" but instead it gives me msg. about static
} declarations and such ;-)

You mostly lost me here.  If the compiler doesn't handle c++ syntax,
it's not going to be able to tell that a c++ comment is what confused
it; it's just going to cough up a syntax error and possibly some other
errors if it tries to keep on parsing.

Also, zsh's build process depends on being able to recognize some
comment markers and use that information to extract declarations into
automatically-generated header files, so even if the compiler did
understand c++ comments you could get into trouble if you changed the
wrong existing comment into that syntax.  That's probably not what you
are doing anyway.

As a final note, you should direct questions about the zsh internals
to the zsh-workers list instead of to zsh-users.  The latter is for
questions about shell interaction, scripts, etc., though some internal
stuff does cross the boundary in bug report threads.


      reply	other threads:[~2014-10-23  4:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-11 18:53 zsh 5.0.7 Ray Andrews
2014-10-11 20:10 ` Bart Schaefer
2014-10-11 21:46   ` Ray Andrews
2014-10-11 21:56     ` Axel Beckert
2014-10-11 22:43       ` Ray Andrews
2014-10-11 22:01     ` Bart Schaefer
2014-10-12  0:29       ` Ray Andrews
2014-10-13 19:02         ` Greg Klanderman
2014-10-13 22:04           ` Ray Andrews
2014-10-13 22:58             ` Greg Klanderman
2014-10-14  1:17               ` Ray Andrews
2014-10-14 20:12                 ` Greg Klanderman
2014-10-14 20:33                   ` Ray Andrews
2014-10-14 17:20             ` combining .histfiles Ray Andrews
2014-10-14 22:04               ` Bart Schaefer
2014-10-14 22:25                 ` Ray Andrews
2014-10-14 23:55                   ` Bart Schaefer
2014-10-15  1:02                     ` Ray Andrews
2014-10-15  1:09                       ` Kurtis Rader
2014-10-15  1:25                         ` Ray Andrews
2014-10-23  2:58             ` c++ comments Ray Andrews
2014-10-23  4:41               ` Bart Schaefer [this message]

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=141022214120.ZM18075@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).