cpp-netlib-devel — Developers Mailing List

Re: [cpp-netlib-devel] Moving the Parser Implementation to a .cpp

[Dean M. B. <mik...@gm...>]

On Fri, Dec 3, 2010 at 11:17 PM, Nelson, Erik - 2
<eri...@ba...> wrote:
>> Dean Michael Berris wrote on Thursday, December 02, 2010 11:35 PM
>> I think the easiest way to minimize the compile time cost would be to
>> move the Spirit.Qi based parser out to a .cpp and just build and
>> external lib. I'll try to make that happen locally and see how far
>> that goes, and I'll update everyone on what that's going to look like
>> for 0.9 soon as I'm done.
>>
>> Comments, feedback, violent reactions, etc. would be most appreciated.
>>
>
>
> Sounds like a good start.
>

Thanks Erik. :)

> I'm not sure if you've been following or went to any of the MSM stuff
> this year at BoostCon, but that's a pretty sweet implementation if you
> need a state machine in the course of making cpp-netlib.
>

Yes, I did -- and I was there! :D

Unfortunately that's yet another hammer I need to learn to use. The
implementation right now works with a hand-rolled incremental parser
-- it's going to be interesting to see how I (or someone else) can
port that to use Boost.MSM.

The EUML stuff is cool and I'd really like to give that a spin. But, I
don't have the time to much with that part of the implementation yet.
Maybe later on I'll get more familiar with it and start moving the
implementations to use Boost.MSM later on.

-- 
Dean Michael Berris
deanberris.com

Re: [cpp-netlib-devel] Moving the Parser Implementation to a .cpp

[Nelson, E. - 2 <eri...@ba...>]

> Dean Michael Berris wrote on Thursday, December 02, 2010 11:35 PM
> I think the easiest way to minimize the compile time cost would be to
> move the Spirit.Qi based parser out to a .cpp and just build and
> external lib. I'll try to make that happen locally and see how far
> that goes, and I'll update everyone on what that's going to look like
> for 0.9 soon as I'm done.
> 
> Comments, feedback, violent reactions, etc. would be most appreciated.
>

 
Sounds like a good start.

I'm not sure if you've been following or went to any of the MSM stuff
this year at BoostCon, but that's a pretty sweet implementation if you
need a state machine in the course of making cpp-netlib.

Erik

----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. 
Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. 
The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. 

References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: 
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.

Re: [cpp-netlib-devel] Moving the Parser Implementation to a .cpp

[Dean M. B. <mik...@gm...>]

On Fri, Dec 3, 2010 at 4:23 PM, Dean Michael Berris
<mik...@gm...> wrote:
> On Fri, Dec 3, 2010 at 12:34 PM, Dean Michael Berris
> <mik...@gm...> wrote:
>> Hi Guys,
>>
>> I think the easiest way to minimize the compile time cost would be to
>> move the Spirit.Qi based parser out to a .cpp and just build and
>> external lib. I'll try to make that happen locally and see how far
>> that goes, and I'll update everyone on what that's going to look like
>> for 0.9 soon as I'm done.
>>
>
> As promised, here's the associated commit on the 0.9-devel branch --
> hopefully the lower building and testing costs now will lower the
> barrier to usage of the library.
>

https://github.com/mikhailberis/cpp-netlib/commit/b74ce4c5deadaeb74d997919efea3141d71040cd

shortened: http://goo.gl/HVDQb

-- 
Dean Michael Berris
deanberris.com

Re: [cpp-netlib-devel] Moving the Parser Implementation to a .cpp

[Dean M. B. <mik...@gm...>]

On Fri, Dec 3, 2010 at 12:34 PM, Dean Michael Berris
<mik...@gm...> wrote:
> Hi Guys,
>
> I think the easiest way to minimize the compile time cost would be to
> move the Spirit.Qi based parser out to a .cpp and just build and
> external lib. I'll try to make that happen locally and see how far
> that goes, and I'll update everyone on what that's going to look like
> for 0.9 soon as I'm done.
>

As promised, here's the associated commit on the 0.9-devel branch --
hopefully the lower building and testing costs now will lower the
barrier to usage of the library.

Jeroen/Glyn, I had to make a lot of changes, and one of them is the
removal of the references in the URI tuple handling. I'm not sure I
did the right things here, but it would be greatly appreciated if both
of you can take a look at what I've done.

> Comments, feedback, violent reactions, etc. would be most appreciated.

This is still definitely true, looking forward to what the people on
the other side of the world will have to say.

Thanks and I hope this helps.

(Also, to those watching, 0.9 will not be a header-only release
anymore, so the whole documentation will have to be overhauled. Help
in that regard would really be appreciated.)

-- 
Dean Michael Berris
deanberris.com

Re: [cpp-netlib-devel] Eclipse CDT cannot compile cpp-netlib

[Dean M. B. <mik...@gm...>]

On Fri, Dec 3, 2010 at 1:07 PM, Chatsiri Ratana <ins...@gm...> wrote:
> I using MinGw.I got the version of GCC from command line by "--version".

Please don't top-post.

Please try 0.8 instead of 0.7 -- you can download that from
https://github.com/cpp-netlib/cpp-netlib/downloads and let me know if
that works better.

Also, please provide a minimal .cpp file that reproduces the problem
so that I can better diagnose what's going on.

-- 
Dean Michael Berris
deanberris.com

Re: [cpp-netlib-devel] Eclipse CDT cannot compile cpp-netlib

[Chatsiri R. <ins...@gm...>]

I using MinGw.I got the version of GCC from command line by "--version".

C:\Documents and Settings\chatsiri.rat>gcc --version

gcc (TDM-2 mingw32) 4.4.1

Copyright (C) 2009 Free Software Foundation, Inc.

This is free software; see the source for copying conditions.  There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


On Fri, Dec 3, 2010 at 10:20 AM, Dean Michael Berris <mik...@gm...
> wrote:

> On Fri, Dec 3, 2010 at 11:01 AM, Chatsiri Ratana <ins...@gm...>
> wrote:
> > Hello
> > I was compiled cpp-netlib version 0.7 by insert an include
> > folder(C:/cpp-netlib-0.7/cpp-netlib-0.7/boost/)  int project. It's show
> an
> > error in link below.
> > https://gist.github.com/723219
>
> Thanks, it looks like you're using GCC -- is this Cygwin or MinGW?
>
> The code is supposed to work, it's standard C++, but the problem is
> the GCC you may be using is an older version that cannot handle this
> kind of template metaprogramming. Can you say what version of GCC are
> you using?
>
> Also, it would be great if you can also show a simple test case that
> can reproduce this error.
>
> --
> Dean Michael Berris
> deanberris.com
>
>
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> Cpp-netlib-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cpp-netlib-devel
>



-- 
:--------------------------------------------------------
weblog  :http://www.chatsiri.com,profile:
http://www.linkedin.com/in/chatsiri

[cpp-netlib-devel] Moving the Parser Implementation to a .cpp

[Dean M. B. <mik...@gm...>]

Hi Guys,

I think the easiest way to minimize the compile time cost would be to
move the Spirit.Qi based parser out to a .cpp and just build and
external lib. I'll try to make that happen locally and see how far
that goes, and I'll update everyone on what that's going to look like
for 0.9 soon as I'm done.

Comments, feedback, violent reactions, etc. would be most appreciated.

HTH

-- 
Dean Michael Berris
deanberris.com

Re: [cpp-netlib-devel] Http post example

[Dean M. B. <mik...@gm...>]

On Fri, Dec 3, 2010 at 11:04 AM, Raindog <ra...@ma...> wrote:
> "Dean Michael Berris" <mik...@gm...> wrote:
>>
>>Actually this isn't an HTTP POST, but rather an HTTP GET request with
>>the query parameter supplied. This would work for what you intend to
>>do:
>>
>>  http::client client;
>>  http::client::request
>>request("http://www.mysite.com/site.cgi?foo=bar&baz=quid");
>>  http::client::response response = client.get(request);
>>
>>HTH
>>
>
> I realize now that after your response that I need also to send a file, I am trying essentially to fill out a web form w/ a file upload element, along with some options, hence why I thought it was a POST. I apologize for not being clear
>

Re-arranging your response for posterity. ;)

So even in that situation, instead of using 'client.get' you can use
'client.post', and then put the file contents as part of the request.
This isn't easily supported at the moment because the client requires
that the contents be in a string. If your file is large (multiple
megabytes) it is an issue and I'm going to address that limitation in
the coming 0.9 release.

Let me know if you need any more information regarding how to make the
file contents part of the POST request.

-- 
Dean Michael Berris
deanberris.com

Re: [cpp-netlib-devel] Eclipse CDT cannot compile cpp-netlib

[Dean M. B. <mik...@gm...>]

On Fri, Dec 3, 2010 at 11:01 AM, Chatsiri Ratana <ins...@gm...> wrote:
> Hello
> I was compiled cpp-netlib version 0.7 by insert an include
> folder(C:/cpp-netlib-0.7/cpp-netlib-0.7/boost/)  int project. It's show an
> error in link below.
> https://gist.github.com/723219

Thanks, it looks like you're using GCC -- is this Cygwin or MinGW?

The code is supposed to work, it's standard C++, but the problem is
the GCC you may be using is an older version that cannot handle this
kind of template metaprogramming. Can you say what version of GCC are
you using?

Also, it would be great if you can also show a simple test case that
can reproduce this error.

-- 
Dean Michael Berris
deanberris.com

Re: [cpp-netlib-devel] Http post example

[Raindog <ra...@ma...>]

Thanks, and sorry for the top post, my email client on my phone only supports top posting.

I realize now that after your response that I need also to send a file, I am trying essentially to fill out a web form w/ a file upload element, along with some options, hence why I thought it was a POST. I apologize for not being clear

"Dean Michael Berris" <mik...@gm...> wrote:

>Hi,
>
>On Fri, Dec 3, 2010 at 9:42 AM, Raindog <ra...@ma...>
>wrote:
>> Hello,
>>
>> I am wondering if someone can show me a minimalist http post example,
>at least how to add the query string parameters to the existing
>example. IE how to post the equivalent of:
>>
>> Http://www.mysite.com/site.cgi?foo=bar&baz=quid
>>
>
>Actually this isn't an HTTP POST, but rather an HTTP GET request with
>the query parameter supplied. This would work for what you intend to
>do:
>
>  http::client client;
>  http::client::request
>request("http://www.mysite.com/site.cgi?foo=bar&baz=quid");
>  http::client::response response = client.get(request);
>
>HTH
>
>-- 
>Dean Michael Berris
>deanberris.com
>
>------------------------------------------------------------------------------
>Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
>Tap into the largest installed PC base & get more eyes on your game by
>optimizing for Intel(R) Graphics Technology. Get started today with the
>Intel(R) Software Partner Program. Five $500 cash prizes are up for
>grabs.
>http://p.sf.net/sfu/intelisp-dev2dev
>_______________________________________________
>Cpp-netlib-devel mailing list
>Cpp...@li...
>https://lists.sourceforge.net/lists/listinfo/cpp-netlib-devel

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

[cpp-netlib-devel] Eclipse CDT cannot compile cpp-netlib

[Chatsiri R. <ins...@gm...>]

Hello

I was compiled cpp-netlib version 0.7 by insert an include folder(
C:/cpp-netlib-0.7/cpp-netlib-0.7/boost/)  int project. It's show an error in
link below.
https://gist.github.com/723219
-- 
:--------------------------------------------------------
weblog  :http://www.chatsiri.com,profile:
http://www.linkedin.com/in/chatsiri

Re: [cpp-netlib-devel] Http post example

[Dean M. B. <mik...@gm...>]

Hi,

On Fri, Dec 3, 2010 at 9:42 AM, Raindog <ra...@ma...> wrote:
> Hello,
>
> I am wondering if someone can show me a minimalist http post example, at least how to add the query string parameters to the existing example. IE how to post the equivalent of:
>
> Http://www.mysite.com/site.cgi?foo=bar&baz=quid
>

Actually this isn't an HTTP POST, but rather an HTTP GET request with
the query parameter supplied. This would work for what you intend to
do:

  http::client client;
  http::client::request
request("http://www.mysite.com/site.cgi?foo=bar&baz=quid");
  http::client::response response = client.get(request);

HTH

-- 
Dean Michael Berris
deanberris.com

[cpp-netlib-devel] Http post example

[Raindog <ra...@ma...>]

Hello,

I am wondering if someone can show me a minimalist http post example, at least how to add the query string parameters to the existing example. IE how to post the equivalent of:

Http://www.mysite.com/site.cgi?foo=bar&baz=quid

Thanks!
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Re: [cpp-netlib-devel] Example hello_world_server.cpp broken in v0.8?

[Dean M. B. <mik...@gm...>]

On Wed, Dec 1, 2010 at 4:57 PM, Glyn Matthews <gly...@gm...> wrote:
> Dean, Erik,
>
> On 30 November 2010 17:46, Dean Michael Berris <mik...@gm...>
> wrote:
>>
>> Patches welcome. ;)
>
>
> I added this to the issue tracker:
> https://github.com/cpp-netlib/cpp-netlib/issues/issue/8/#issue/8/comment/579978

Cool, thanks Glyn.

Now I'm not sure how to do the scripting in a cross-platform manner --
maybe use Python or something, not really sure how to go about that.

Ideas, and of course patches would be very much welcome. :)

-- 
Dean Michael Berris
deanberris.com

Re: [cpp-netlib-devel] Example hello_world_server.cpp broken in v0.8?

[Glyn M. <gly...@gm...>]

Dean, Erik,

On 30 November 2010 17:46, Dean Michael Berris <mik...@gm...>wrote:

> On Wed, Dec 1, 2010 at 12:43 AM, Nelson, Erik - 2
> <eri...@ba...> wrote:
> > Dean Michael Berris wrote:
> >>
> >> Or just missing an include. It's odd that this doesn't show up in GCC.
> >> Can you try the above include directive, and report back if it fixes
> >> things?
> >>
> >
> > In my experience, there are quite a few cases like this in cpp-netlib...
> is there some automated tool that can check to make sure the proper headers
> are included?
> >
>
> The real reason for this is that in reality, I want people to just
> include the "supported" header -- which in this case should be
> boost/network/include/http/server.hpp.
>
> There's really no other explanation -- not sure if that was what
> Christoffer did, and if so that would be a bug.
>
> > A script that just tried to compile each file by itself should do the
> trick, right?
> >
>
> Patches welcome. ;)
>


I added this to the issue tracker:

https://github.com/cpp-netlib/cpp-netlib/issues/issue/8/#issue/8/comment/579978

Thanks,
Glyn

Re: [cpp-netlib-devel] URI: Spirit Compile Times

[Dean M. B. <mik...@gm...>]

On Wed, Dec 1, 2010 at 3:51 AM, Jeroen Habraken <vex...@gm...> wrote:
>
> On 30 November 2010 17:38, Dean Michael Berris <mik...@gm...> wrote:
>>
>> I see that the URI code has a lot of rules (>5) which can still be
>> reduced into a single rule. Jeroen/Glyn can you try and look at
>> reducing the number of rules and consolidate to just one rule just to
>> see whether it would help reduce the compile times?
>>
>> Thanks in advance and I hope to hear what you guys think about trying
>> that out. I might do that on my own but getting time lately to work on
>> cpp-netlib ironically just got really hard.
>>
>
> There is a best practices documentation addendum here:
> http://boost-spirit.com/home/articles/doc-addendum/best-practices/,
> which states:
>
> "Avoid complex rules. Rules with complex definitions hurt the compiler
> badly. We’ve seen rules that are more than a hundred lines long and
> take a couple of minutes to compile. On some compilers, experience
> shows that the compile time is exponential in relation to the RHS
> expression length. C++ compilers were not designed to handle such big
> expressions and some just couldn’t cope (crashes). It is always best
> to break complex rules into more manageable, easier to digest parts.
> Doing so also makes the rules more readable."
>

Yes, that is true, but there was a mailing list discussion about the
cost of doing assignments to rules which basically invokes the Proto
evaluator. This kills the compiler because the Proto evaluation is a
full-on compiler in itself. Invoking it multiple times is a bigger
problem than having it deal with a sufficiently complex rule (in our
case it's really just a sequencing of optionals, which shouldn't
require too much mumbo-jumbo on the Proto side I imagine).

> and I've always understood is that multiple simple rules are
> preferable to a single complex rule. However, if I find time I'll look
> into combining some rules and testing whether it helps the
> compile-time, it shouldn't be to hard.
>

Yep they were -- especially in the Classic days IIRC. But with Qi and
the Proto stuff, the rule assignments get more expensive than the more
complex rules if I get my Proto correctly.

I'll look forward to your experiments and hopefully we can address
some of the compile time concerns as I go head-on into 0.9.

Thanks for looking into it Jeroen!

-- 
Dean Michael Berris
deanberris.com

Re: [cpp-netlib-devel] http server request path()

[Dean M. B. <mik...@gm...>]

Hi Tim,

On Wed, Dec 1, 2010 at 7:41 AM, Timothy Stewart
<tim...@gm...> wrote:
> I apologize in advance, my C++ is fairly weak.  I was trying to make a
> simple http server using cpp netlib v.0.8.  The first problem I ran into was
> the undefined "_or" problem, which I got around by including foreach.hpp (I
> believe the other thread recommended #include <boost/mpl/or.hpp> which I'm
> sure is a more direct solution).

Yes, that should really be addressed in a point release. I'll commit
that change and package up 0.8.1 appropriately.

>
> // CPPNetLibTest.cpp : Defines the entry point for the console application.
> //
> #include "stdafx.h"
> #include <boost/foreach.hpp>
> #include <boost/network/include/http/server.hpp>
>
> struct handler_type;
> typedef boost::network::http::server<handler_type> http_server;
> struct handler_type {
>     void operator()(
>         http_server::request const & request,
>         http_server::response & response
>     ) {
>         std::string pathstr = path(request);
> // do something here depending on the path requested.

Here, instead of path(request), do destination(request).

I'll try to make the above work too, I hadn't thought about the
symmetry between a client request and a server request. I'll see if
that can make it into 0.8.1 too.

HTH

-- 
Dean Michael Berris
deanberris.com

[cpp-netlib-devel] http server request path()

[Timothy S. <tim...@gm...>]

I apologize in advance, my C++ is fairly weak.  I was trying to make a
simple http server using cpp netlib v.0.8.  The first problem I ran into was
the undefined "_or" problem, which I got around by including foreach.hpp (I
believe the other thread recommended #include <boost/mpl/or.hpp> which I'm
sure is a more direct solution).

Anyhow, I haven't been able to figure out how to fix my second problem.
 Here is the code, which I've stripped down to the "Hello World" example.
 I'm working with Visual Studio 2008.

I receive the error:

Error 1 error C2039: 'path' : is not a member of
'boost::network::http::basic_request<boost::network::http::tags::http_server>'
d:\dev\c++\lib\boost\boost_1_44\boost\network\protocol\http\message\wrappers\path.hpp
CPPNetLibTest 27


I think it has something to do with the forward declaration of basic_request
in path.hpp, and the fact that path.hpp tries to access path() before it is
fully defined (but like I said, my C++ is weak).  I tried replacing the
forward declaration with various attempts at a #include, but I ran into
hosts of other problems with that.

Can anyone recommend an easy solution?

Thanks in advance.

- Tim Stewart.


// CPPNetLibTest.cpp : Defines the entry point for the console application.
//

#include "stdafx.h"

#include <boost/foreach.hpp>

#include <boost/network/include/http/server.hpp>


struct handler_type;
typedef boost::network::http::server<handler_type> http_server;

struct handler_type {
    void operator()(
        http_server::request const & request,
        http_server::response & response
    ) {
        std::string pathstr = path(request);
// do something here depending on the path requested.
    }
};

int _tmain(int argc, _TCHAR* argv[])
{

handler_type handler;
http_server server("127.0.0.1", "8000", handler);
server.run();

return 0;
}

Re: [cpp-netlib-devel] URI: Spirit Compile Times

[Jeroen H. <vex...@gm...>]

Hi,

On 30 November 2010 17:38, Dean Michael Berris <mik...@gm...> wrote:
> Hi Everyone,
>
> I recently remembered general advice about how to keep the compile
> times down with Spirit.Qi and one of the general tips was to limit the
> number of rules you have. The rationale was if you were writing a
> parser and had a lot of rule assignments, you were essentially
> invoking Proto's evaluation when assigning to a rule.
>
> I see that the URI code has a lot of rules (>5) which can still be
> reduced into a single rule. Jeroen/Glyn can you try and look at
> reducing the number of rules and consolidate to just one rule just to
> see whether it would help reduce the compile times?
>
> Thanks in advance and I hope to hear what you guys think about trying
> that out. I might do that on my own but getting time lately to work on
> cpp-netlib ironically just got really hard.
>
> --
> Dean Michael Berris
> deanberris.com
>

There is a best practices documentation addendum here:
http://boost-spirit.com/home/articles/doc-addendum/best-practices/,
which states:

"Avoid complex rules. Rules with complex definitions hurt the compiler
badly. We’ve seen rules that are more than a hundred lines long and
take a couple of minutes to compile. On some compilers, experience
shows that the compile time is exponential in relation to the RHS
expression length. C++ compilers were not designed to handle such big
expressions and some just couldn’t cope (crashes). It is always best
to break complex rules into more manageable, easier to digest parts.
Doing so also makes the rules more readable."

and I've always understood is that multiple simple rules are
preferable to a single complex rule. However, if I find time I'll look
into combining some rules and testing whether it helps the
compile-time, it shouldn't be to hard.

Jeroen

Re: [cpp-netlib-devel] Example hello_world_server.cpp broken in v0.8?

[Dean M. B. <mik...@gm...>]

On Wed, Dec 1, 2010 at 12:43 AM, Nelson, Erik - 2
<eri...@ba...> wrote:
> Dean Michael Berris wrote:
>>
>> Or just missing an include. It's odd that this doesn't show up in GCC.
>> Can you try the above include directive, and report back if it fixes
>> things?
>>
>
> In my experience, there are quite a few cases like this in cpp-netlib... is there some automated tool that can check to make sure the proper headers are included?
>

The real reason for this is that in reality, I want people to just
include the "supported" header -- which in this case should be
boost/network/include/http/server.hpp.

There's really no other explanation -- not sure if that was what
Christoffer did, and if so that would be a bug.

> A script that just tried to compile each file by itself should do the trick, right?
>

Patches welcome. ;)

-- 
Dean Michael Berris
deanberris.com

Re: [cpp-netlib-devel] Example hello_world_server.cpp broken in v0.8?

[Nelson, E. - 2 <eri...@ba...>]

Dean Michael Berris wrote:
> 
> Or just missing an include. It's odd that this doesn't show up in GCC.
> Can you try the above include directive, and report back if it fixes
> things?
> 

In my experience, there are quite a few cases like this in cpp-netlib... is there some automated tool that can check to make sure the proper headers are included?  

A script that just tried to compile each file by itself should do the trick, right?

Erik

----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. 
Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. 
The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. 

References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: 
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.

[cpp-netlib-devel] URI: Spirit Compile Times

[Dean M. B. <mik...@gm...>]

Hi Everyone,

I recently remembered general advice about how to keep the compile
times down with Spirit.Qi and one of the general tips was to limit the
number of rules you have. The rationale was if you were writing a
parser and had a lot of rule assignments, you were essentially
invoking Proto's evaluation when assigning to a rule.

I see that the URI code has a lot of rules (>5) which can still be
reduced into a single rule. Jeroen/Glyn can you try and look at
reducing the number of rules and consolidate to just one rule just to
see whether it would help reduce the compile times?

Thanks in advance and I hope to hear what you guys think about trying
that out. I might do that on my own but getting time lately to work on
cpp-netlib ironically just got really hard.

-- 
Dean Michael Berris
deanberris.com

Re: [cpp-netlib-devel] Example hello_world_server.cpp broken in v0.8?

[Dean M. B. <mik...@gm...>]

On Wed, Dec 1, 2010 at 12:01 AM, Christoffer Mollenhoff
<Mol...@in...> wrote:
> Hi,
>
>> Are you building with CMake?
>
> No, I just created a simple project with the server example and added Boost and cpp-netlib to the list of include folders.
>

Ah, alright. That's good to know. You might want to check out the
asynchronous HTTP server example and see whether that might be better
for your use case. It is after all what's new in 0.8. :)

>> It looks like there's a missing include here. Can you try adding:
>> #include <boost/mpl/or.hpp>
>
> That took care of it. Thanks for the quick assistance!
>

No worries, I'm glad to be able to help.

Glyn, do you think we need a 0.8.1 to address this? It might be
something others might uncover as well.

-- 
Dean Michael Berris
deanberris.com

Re: [cpp-netlib-devel] Example hello_world_server.cpp broken in v0.8?

[Christoffer M. <Mol...@in...>]

Hi,

> Are you building with CMake?

No, I just created a simple project with the server example and added Boost and cpp-netlib to the list of include folders.

> It looks like there's a missing include here. Can you try adding:
> #include <boost/mpl/or.hpp>

That took care of it. Thanks for the quick assistance!

Best regards,
Christoffer M.

Re: [cpp-netlib-devel] Example hello_world_server.cpp broken in v0.8?

[Dean M. B. <mik...@gm...>]

Hi Christoffer,

On Tue, Nov 30, 2010 at 8:50 PM, Christoffer Mollenhoff
<Mol...@in...> wrote:
>
> I’m hitting the following compilation error using Visual Studio 2010 and
> Boost 1.45. The example compiles perfectly using v0.7, however.
>

Are you building with CMake?

>
> 1>c:\cpp-netlib-0.8\boost\network\protocol\http\message\traits\version.hpp(28):
> error C2065: 'or_' : undeclared identifier
>

It looks like there's a missing include here. Can you try adding:

#include <boost/mpl/or.hpp>

At the top of the file, maybe around line 13? That should fix it.

>
> Looks like a using directive got lost on the way somewhere.
>

Or just missing an include. It's odd that this doesn't show up in GCC.
Can you try the above include directive, and report back if it fixes
things?

Thanks and I hope this helps.

-- 
Dean Michael Berris
deanberris.com