I encountered a bug while trying include some file:
--cut
scheme@(guile-user)> (include "aa.scm")
While compiling expression:
ERROR: In procedure string-length: Wrong type argument in position 1
(expecting string): #f
--end
Mark H Weaver wrote:
> Ah, that's good! So perhaps we should just import the relevant gnulib
> module and convert all existing uses of SCM_NORETURN to use _Noreturn
> instead. What do you think?
I think it'll work; at least, _Noreturn has worked for Gnulib fairly well
since we introduced it in s
Paul Eggert writes:
> Mark H Weaver wrote:
>> Looking at C11, it appears that _Noreturn belongs before the function
>> return type, whereas __attribute__ (__noreturn__) and SCM_NORETURN goes
>> after the formal parameter list. So I don't see how your proposed
>> workaround can work properly.
>
>
Mark H Weaver wrote:
> Looking at C11, it appears that _Noreturn belongs before the function
> return type, whereas __attribute__ (__noreturn__) and SCM_NORETURN goes
> after the formal parameter list. So I don't see how your proposed
> workaround can work properly.
__attribute__ (__noreturn__) c
Bruce Korb writes:
> On 11/13/13 23:52, Mark H Weaver wrote:
>> FYI, I recently made precisely that change to the stable-2.0 branch,
>> which will become Guile 2.0.10:
>>
>> http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=36c40440078c005cd5e239cca487d29f6f60007d;hp=b1fe20c24ccb3804
On 11/13/13 23:52, Mark H Weaver wrote:
'_Noreturn' is a bit ugly; if you don't care about
MSVC, then __attribute__((__noreturn__)) is
a good way to go.
Hi Paul,
Thanks. As mentioned in the GCC pages, using the prefix/suffix
of "__" is the right way to go -- for Guile.
FYI, I recently made
