[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: RE: [ANN] Lua 5.3.0 (rc4) now available
- From: Thijs Schreijer <thijs@...>
- Date: Wed, 7 Jan 2015 21:31:34 +0000
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:email@example.com] On
> Behalf Of Roberto Ierusalimschy
> Sent: woensdag 7 januari 2015 12:44
> To: Lua mailing list
> Subject: Re: [ANN] Lua 5.3.0 (rc4) now available
> > One remark; as LUA_COMPAT_ALL has been deprecated, in favour of
> > version specific ones, would it be possible to break the build when it
> > has been defined? Maybe a silly idea, but it would safeguard someone
> > from expecting compatibility and not getting it.
> I think you are kind of glorifing LUA_COMPAT_ALL. LUA_COMPAT_ALL never
> meant "keep full compatibility with previous versions". It meant keep
> some compatibility with the immediate previous version where possible,
> for a loose interpretation of "possible". To expect compatibility just
> because this macro is defined is (and has always been) unwise.
> -- Roberto
Your answer basically confirms what LHF said before. And I understand this. And I also agree regarding the unwise part. It's just that I made this mistake, and someone else (didn't look up that message in the archive) did that as well last week.
So that is twice for just an RC. Breaking the build would not harm anyone, but might benefit some.
I updated my Windows build script  yesterday to now include the 5.2 specific one when building 5.3, mimicking the default make file behaviour. So I won't be doing that again :)