Re: What's the purpose of the define "LUA_CORE"

[Seppl Vorderhörer <Seppl.Vorderhoerer@...>]

Am 30.09.2012 17:41, schrieb liam mail:
> On 30 September 2012 16:32, liam mail <liam.list@googlemail.com> wrote:
> > On 30 September 2012 15:34, Seppl Vorderhörer
> > <Seppl.Vorderhoerer@t-online.de> wrote:
> > > LUA_CORE
> > This leads for me to two questions:
> > 1.) Can this switch not be also lead to problems in "normal" C code
> > not poking around in internals of Lua?
> > Not that I am aware of.
> > 2.) Why is this switch necessary at all? Why would I want code to
> > "know" that it's part of the core and behave differently?
> > LUA_CORE as you have seen defines other internally used macros if it
> > is defined and this is not what is wanted when a user simply includes
> > the public API headers.
> >
> > > Fixing this behaviour is easy: Either compiling with LUA_CORE
> > This is not surprising as you are using internal details.
> >
> > Liam
> Here is a similar request for information earlier in the year.
> http://thread.gmane.org/gmane.comp.lang.lua.general/89361/
>
> Liam
Thanks for the thread. So I see a similar question (not the same) has 
been discussed before - even if the question, why LUA_CORE is necessary 
has also not been answered.

No thanks for your comments "this is not surprising as you are using 
internal details", sorry.
This does not answer any question and is not helpful at all (although 
not surprising... :-D).

I even think, it is not correct in this special context: Despite the 
discussion if one should or should not use any internals of Lua: This 
was not the question.
The question was whether this dependency on LUA_CORE is necessary or 
might on the other hand even pose some risk also in code NOT using 
internals.