edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Mix
Date: Tue, 24 Dec 2013 06:48:50 -0800	[thread overview]
Message-ID: <87d2kmb8z1.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20131124043018.eklhad@comcast.net> (Karl Dahlke's message of "Tue, 24 Dec 2013 04:30:18 -0500")

Here's another replacement we will need.  "this" is a keyword in C++, so
we cannot use it as a name for function arguments in files that we
expect to compile with a C++ compiler.  Same goes for "new", but I don't
think there are any new's in jsdom.c or jsloc.c.  I'll find and fix uses
of this and new in these two files.

-- Chris

  parent reply	other threads:[~2013-12-24 14:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-24  9:30 Karl Dahlke
2013-12-24 13:09 ` Chris Brannon
2013-12-24 14:48 ` Chris Brannon [this message]
2013-12-24 15:30 ` Adam Thompson
  -- strict thread matches above, loose matches on Subject: below --
2013-12-23 15:36 Karl Dahlke
2013-12-24  8:52 ` Adam Thompson

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=87d2kmb8z1.fsf@mushroom.PK5001Z \
    --to=chris@the-brannons.com \
    --cc=edbrowse-dev@lists.the-brannons.com \
    /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 NNTP newsgroup(s).