lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

On Friday, February 21, 2014, René Rebe <> wrote:
On Feb 21, 2014, at 14:09 , steve donovan wrote:

On Fri, Feb 21, 2014 at 2:41 PM, René Rebe <> wrote:
I do not remember being among the group of "all" that want to cover a data
corruption bug with a change of the manual, ... :-/

You've proposed a solution, but cannot insist on immediately getting
an answer; generally the Lua team do not accept patches directly.
People can refer to this thread and patch their Lua if they feel the

To continue to irritate people is not the best way to make a contribution.

I did not insist not an "answer", actually already wanted to long give
up replying to this thread, and only commented to the irritating replies
that came in.

But, there's nothing stopping you from creating a little C extension
that implements getline for Lua.  It's certainly not a problem which
people hit very often...

I already mentioned that the change already went into our local Lua
tree, … so bug long solved for us™.

 ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin | | | |

Shame on me for adding to this after the "stop" button was pressed. 

This is very much a human problem, not a technical one. Correct behavior can be defined by many smart people and the answers will not be the same. 

The specifications and standards are interesting, and not the  whole story. 

What behavior does the average scripting user expect?

Is an error in \0 possible?