Josh Goebel

Anyone know the status of this? Really need it for test runners... Some errors are impossible to debug without a working stack trace with a line number (such as `method...

We need an `.editor_config` and some agreement on how excess whitespace is handled (in general) so we can fix this once and for all... trailing whitespace issues is a unnecessary...

I took another pass at this.

Can we fix this with a simple: ```c #define ERROR_MESSAGE_SIZE (80 + MAX_VARIABLE_NAME + MAX_VARIABLE_NAME + 15) ``` The problem is we need to allow for MAX_VARIABLE_NAME to be included...

My thumbs up was for the functionality itself. I think this improves the readability. The implementation could likely be improved further, agreed.

Could a quick example be given here of when this is useful in real life since those other two threads are super super long. :)

> mhermier put two in the OP. They were added after I requested a small example. :) But yes it's all quite clear now what this feature would be useful...

> *** stack smashing detected ***: terminated Is this a patch you have or a compiler option? If a patch is there a link?

> As this, for security reasons, I would say no. This would allow to compromise modules contents. Can you explain further or give an example?

I see what you mean but using modules as a "security context" seems pretty shaky ground to begin with if we assume someone can still evaluate ANY arbitrary code in...