Thus spake Ralf Grosse-Kunstleve:
>
> It looks like you inserted an extra const (I don't see it in the current
> tutorial) ...
>
> char const * const greet() {
>
> It should work if you remove it.
Ha! You're correct. The example program was so short that I just retyped
it, and I made the pointe
Oops, I meant to mark the extra const with a color:
char const * *const* greet() {
On Thu, Jul 5, 2012 at 7:57 AM, Ralf Grosse-Kunstleve wrote:
> It looks like you inserted an extra const (I don't see it in the current
> tutorial) ...
>
> char const * const greet() {
>
> It should work if you r
It looks like you inserted an extra const (I don't see it in the current
tutorial) ...
char const * const greet() {
It should work if you remove it.
Ralf
On Thu, Jul 5, 2012 at 3:21 AM, Joel Uckelman wrote:
> I'm trying to compile the example from the Boost Python docs without
> success.
>
>
On 5 July 2012 13:10, Joel Uckelman wrote:
> Do you know why Boost Python complains about returning a char const*?
>
When returning a pointer, you have to tell Boost::Python what to do with
it. The most important issue is one of ownership. Once the pointer has been
returned as a Python object in
Thus spake Sybren A. Stüvel:
>
> Hi Joel,
>
> On 5 July 2012 12:21, Joel Uckelman wrote:
>
> > I'm trying to compile the example from the Boost Python docs without
> > success. [...]
> >
>
> There are many ways in which you can fix this. I think the easiest one from
> an I'm-just-starting-so-
Hi Joel,
On 5 July 2012 12:21, Joel Uckelman wrote:
> I'm trying to compile the example from the Boost Python docs without
> success. [...]
>
There are many ways in which you can fix this. I think the easiest one from
an I'm-just-starting-so-please-give-me-a-simple-hello-world-program point
of
