RE: Hooks for I/O, memory, etc?

[Pyrogon Public <public@...>]

I'm in 100% agreement with Jason on this.  Small things like this really
do help with the longer term view of getting Lua adopted -- the easier
it is to integrate into projects, the less resistance there will be, and
forcing people to edit the code every time there's an update is a bit
much to ask.  Of course, hardcore Lua-files won't have a problem with
it, but they're not the people that we're trying to evangelize.

Brian

> -----Original Message-----
> From: owner-lua-l@tecgraf.puc-rio.br 
> [mailto:owner-lua-l@tecgraf.puc-rio.br] On Behalf Of J. Perkins
> Sent: Monday, June 10, 2002 11:55 AM
> To: Multiple recipients of list
> Subject: Re: Hooks for I/O, memory, etc?
> 
> 
> My preference is to make as few changes to Lua -- or any third-party 
> code -- as possible. Callbacks for I/O and memory allocation seems, 
> to me anyway, obvious for an embedded API. Is there any drawback to 
> it? Sure I have a working implementation now, but I went through a 
> fair amount of grief trying to hunt down the proper places to change 
> things in the source, none of which was documented anywhere. I 
> haven't tried upgrading past 4.1w1, because then I'll have to redo 
> all of the changes. This seems like a good "bang for the buck" from 
> a usability standpoint. At the very least, can we get some 
> documentation on what needs to be changed for each case?
> 
> Just my $0.02 of course.
> 
> Jason