Le 01/04/2015 00:14, Nick Dokos a écrit :
I was thinking of an ob-C.el customizable variable that is set by
default to some useful list of includes, not file-settable things.
But I'm probably the last person you should ask about what is useful
here. Real users should speak up.
I think
Hello,
Thierry Banel tbanelweb...@free.fr writes:
Ok, 100% of votes are for the removal of wired #includes.
Here is the patch. Tests are changed accordingly.
Applied. Thank you.
IMO, it would be better than the current situation, but I wonder if
it makes sense to have a global default
Le 31/03/2015 12:07, Nicolas Goaziou a écrit :
IMO, it would be better than the current situation, but I wonder if
it makes sense to have a global default setting containing the
three files, but one which the user can customize; any :includes
parameters would augment the default.
That would
Thierry Banel tbanelweb...@free.fr writes:
Le 31/03/2015 12:07, Nicolas Goaziou a écrit :
IMO, it would be better than the current situation, but I wonder if
it makes sense to have a global default setting containing the
three files, but one which the user can customize; any :includes
Thierry Banel tbanelweb...@free.fr writes:
Hi Robert
Those #includes were a proposal I did long ago.
The purpose was to make short scripts even shorter with default
#includes that everybody uses.
Your use-case is worth considering.
If this cause trouble, it is easy to remove the includes.
Ok, 100% of votes are for the removal of wired #includes.
Here is the patch. Tests are changed accordingly.
Thierry
Le 30/03/2015 16:39, Nick Dokos a écrit :
IMO, it would be better than the current situation, but I wonder if
it makes sense to have a global default setting containing the
I must admit I am not a fan of the proposed changes to ob-C.el which seem to
insert
#include string.h
#include stdio.h
#include stdlib.h
during a tangle operation, without option. Currently, I am using C mode to
tangle source written in GLSL (OpenGL shading language), which is
Hi Robert
Those #includes were a proposal I did long ago.
The purpose was to make short scripts even shorter with default
#includes that everybody uses.
Your use-case is worth considering.
If this cause trouble, it is easy to remove the includes.
To keep existing scripts working, an :includes
