On 15 August 2015 at 11:35, Miguel Di Ciurcio Filho
mig...@instruct.com.br wrote:
On Thu, Aug 13, 2015 at 9:02 PM, Ryan Coleman r...@puppetlabs.com wrote:
As for the reason, we’re spending some time thinking about how to model
multi-node configurations. Though we’re a couple of months away from
On Thu, Aug 13, 2015 at 9:02 PM, Ryan Coleman r...@puppetlabs.com wrote:
As for the reason, we’re spending some time thinking about how to model
multi-node configurations. Though we’re a couple of months away from
concrete details, we know enough to begin to signal the reservation of new
On Thu, Aug 13, 2015 at 3:28 PM, Ryan Coleman r...@puppetlabs.com wrote:
On Thu, Aug 13, 2015 at 3:10 PM, Chris Rigby squ...@radioglitch.com
wrote:
My issue in particular is related to a bug introduced into the future
parser in 3.8.2.
The bug breaks compilation when using a reserved
My issue in particular is related to a bug introduced into the future
parser in 3.8.2.
The bug breaks compilation when using a reserved keyword as a classname
when the future parser is enabled.
See https://tickets.puppetlabs.com/browse/PUP-5036
On Thursday, 13 August 2015 21:24:36 UTC+1,
On Thu, Aug 13, 2015 at 3:10 PM, Chris Rigby squ...@radioglitch.com wrote:
My issue in particular is related to a bug introduced into the future
parser in 3.8.2.
The bug breaks compilation when using a reserved keyword as a classname
when the future parser is enabled.
See
On Thursday, August 13, 2015 at 9:57:31 AM UTC-5, Chris Rigby wrote:
Hi,
So I have a class called `application`, and literally hundreds of
subclasses called `application::something` and now I've just learnt that
'application' is now a reserved keyword in a point release. (3.8.2).
