Iterator "convertable to" problem

[Martin Sebor]

chris jefferson wrote:
...
> Thanks. I'm still trying to get an exact feel for how much I need to 
> read what is written, and how much I need to apply common sense :)

It's a delicate balance ;-)

> 
>> * Use c++std-ping@accu.org to retrieve archived messages.
> 
> 
> Hmm.. I'm not entirely sure how this works and couln't find a guide... 
> any pointers?

Just send an email to the daemon. It will reply with instructions
on how to use it, like this:

-------- Original Message --------
Date: Fri, 17 Sep 2004 17:47:24 +0100 (BST)
From: Sendmail Default User <mailnull@accu.org>
To: Martin Sebor <sebor@roguewave.com>

To: Martin Sebor <sebor@roguewave.com>
Subject: auto-reply from C++ Standards Committee `ping' daemon
From: c++std=ping@accu.org
Sender: c++std-ping@accu.org
Reply-To: c++std-postmaster@accu.org
Errors-To: c++std-postmaster@accu.org

This message comes to you courtesy of the C++ Standards
`ping' daemon.  The purpose of this daemon is to give you
an automatic way of verifying your electronic address.

You can activate the daemon by sending electronic mail to

	c++std-ping@accu.org

The daemon will auto-reply to every message it receives.
Therefore, if you send a message to c++std-ping@accu.org
and do not receive a reply, something is wrong.

That reply takes one of three forms:

	1. If the daemon does not recognize a request in the
	input message, it will send the message you are reading now
	back to what it thinks is the return address.  This may
	not be the best way to get a message back to you, and in some
	cases it may not even work.  In any event, the msssage
	will contain the address that the daemon thinks it saw.

	In this case, the message will appear to come from
	c++std=ping@accu.org (or something equivalent to
	that). Note the = instead of -; this is to forestall
	forwarding loops.

	2. If the daemon recognizes a `ping' request in the input
	message, it will send a shorter message to the address
	shown in that request.  A request is the first line of the form

		ping return-address

	where `return-address' is the address you want to test.
	There must not be any leading white space in the line
	(so that, for example, this message itself will not be
	interpreted as containing a request).  Only one request
	per message, please!

	In this case, the message will appear to come from the
	return address the daemon obtained from the network(!).
	The purpose of that is so that if the attempt fails,
	perhaps the failure message will be successfully forwarded
	back to you and you can figure out what went wrong.

	3. If the daemon does not find any `ping' requests in the
	message, it will search for requests for messages from the
	archive.  An example of such a request is

		send c++std-core-27

	which will, of course, send the 27th message in the
	c++std-core archive.  Requests for non-existent messages
	are quietly ignored.  Requests for messages in non-existent
	groups are noisily ignored.  If you want multiple messages,
	you must have one input line for each message you want;
	this is to avoid making it too easy for people to request
	gigantic piles of goo by accident.  You can have multiple
	`send' requests in your input; the only restriction is
	that each request nominate only a single message.

The available mailing lists and the
corresponding highest message identifiers are:

	mailing list address             highest message identifier

	c++std-admin@accu.org	 c++std-admin-1149
	c++std-all@accu.org	 c++std-all-2833
	c++std-comm@accu.org	 c++std-comm-8
	c++std-compat@accu.org	 c++std-compat-956
	c++std-core@accu.org	 c++std-core-10640
	c++std-edit@accu.org	 c++std-edit-905
	c++std-embed@accu.org	 c++std-embed-4
	c++std-env@accu.org	 c++std-env-563
	c++std-ext@accu.org	 c++std-ext-7049
	c++std-ibof@accu.org	 c++std-ibof-4
	c++std-intl@accu.org	 c++std-intl-221
	c++std-liaison@accu.org	 c++std-liaison-0
	c++std-lib@accu.org	 c++std-lib-14261
	c++std-migration@accu.org	 c++std-migration-72
	c++std-news@accu.org	 c++std-news-38
	c++std-perf@accu.org	 c++std-perf-266
	c++std-rationale@accu.org	 c++std-rationale-11
	c++std-syntax@accu.org	 c++std-syntax-349
	c++std-ustag@accu.org	 c++std-ustag-13

I know this is complicated.  Networks are complicated.  That's life.
If you can't figure this out, please contact me:


				Andrew Koenig
				ark@acm.org
				164 Gates Avenue
				Gillette, New Jersey 07933-1708  USA

				+1 908 647 3508 (voice)
				+1 908 647 3575 (fax)