From: Chris Brannon <chris@the-brannons.com>
To: Adam Thompson <arthompson1990@gmail.com>
Cc: Karl Dahlke <eklhad@comcast.net>, Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] edbrowse and edbrowse-js not communicating
Date: Sat, 19 Dec 2015 04:58:15 -0800 [thread overview]
Message-ID: <87oadmh9y0.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20151219123743.GC2770@122oven.adamthompson.me.uk> (Adam Thompson's message of "Sat, 19 Dec 2015 12:37:43 +0000")
Adam Thompson <arthompson1990@gmail.com> writes:
> Ok, that makes sense, though I'm surprised we can't check at configure time if
> the version of tidy defines the symbols (and macros) we expect.
Sure, we can check for symbols. If the library defines
tidyLibraryVersion, it is tidy-html5. If it doesn't, then it's some ancient
version of tidy, so throw up our hands and refuse to proceed.
What we won't know without building and running an executable is the
version number of tidy-html5.
Really, we don't know the actual version until runtime. I can build a
program under version 5.1.x and then run it under 5.1.y, just fine,
assuming the public API hasn't changed between x and y.
Hence we should probably do both a compile-time and run-time check.
Compile-time tells us whether we have tidy-html5 or tidy, run0-time
tells us more specifically which version of tidy-html5 we have.
-- Chris
prev parent reply other threads:[~2015-12-19 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 15:32 Chuck Hallenbeck
2015-12-14 18:04 ` Chris Brannon
2015-12-14 18:12 ` Karl Dahlke
2015-12-15 4:55 ` Chris Brannon
2015-12-15 12:58 ` Adam Thompson
2015-12-17 10:44 ` Chris Brannon
2015-12-19 12:37 ` Adam Thompson
2015-12-19 12:58 ` Chris Brannon [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=87oadmh9y0.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=arthompson1990@gmail.com \
--cc=eklhad@comcast.net \
/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).