tiny bugs in 2.6.2?

[Daniel Lee]

Ben, do these all have issues? Let's get things fixed in Stan and not
just have you patch around it.

---------- Forwarded message ----------
From: Ben Goodrich <goodri...@gmail.com>
Date: Sun, Mar 15, 2015 at 10:39 AM
Subject: Re: [stan-dev] Re: conditional compile
To: stan...@googlegroups.com

There were already a couple of other tiny bugs with 2.6.2 that I'm
going to have to patch around.

[Ben Goodrich]

So far, it was just the semicolon thing and the variable length array thing.

It looks as if we can hold off on the macro business.

Ben

[Bob Carpenter]

Yes, Ben's been creating them through issues in Stan.

Should we have a non-public 2.6.3 version of Stan that's
used for StanHeaders?

- Bob

> --
> You received this message because you are subscribed to the Google Groups "stan development mailing list" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to stan-dev+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

[Ben Goodrich]

I can just make a StanHeaders off the develop branch once those two PRs get merged. They shouldn't have had any effect on doxygen or whatever blew up on Jenkins.

Ben

> To unsubscribe from this group and stop receiving emails from it, send an email to stan-dev+unsubscribe@googlegroups.com.

[Daniel Lee]

Ben, both merged.

I think there's something weird going on with the doxygen warning
parser, but I'll try to figure that out later.

>> > an email to stan-dev+u...@googlegroups.com.

>> > For more options, visit https://groups.google.com/d/optout.
>> >
>>

> --
> You received this message because you are subscribed to the Google Groups
> "stan development mailing list" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to stan-dev+u...@googlegroups.com.

[Bob Carpenter]

I noticed in mucking around with Eigen that they have
some #ifdefs just for doxygen, so it looks like the
doxygen parser isn't up to the C++ standard.

- Bob

[Daniel Lee]

I think it might be a bug in the Jenkins warning parser, but I'll keep digging for a while.