Re: C level variants of make-vector / make-string

[Marius Vollmer]

Dirk Herrmann <address@hidden> writes:

> After thinking again about it, it seems that this would mean
> overdoing things for these examples.

Yes, and only be a significant benefit when these functions are called
in inner loops.

> After all, the corresponding functions could as well be made into
> inline functions (as soon as the new C standard is out), [...]

You mean, as soon as all important compilers support this construct,
which is already now, because GCC, well... :-)

Based on this argument, almost all functions should be made inline.  I
don't think we want that.

> > First, I suggest to introduce scm_c_make_string to replace scm_makstr
> > (which would be deprecated).  The function scm_c_make_string would take
> > the size argument as an unsigned long int or scm_sizet.
> 
> This makes sense.  If nobody objects, I will do it.

Yep, you should probably also consider scm_makfrom* and scm_take0str
when you are at it.