betterC and core.stdc modules; betterC and varargs routines

[Derek Fawcus]

On Saturday, 19 October 2024 at 11:40:22 UTC, Salih Dincer wrote:
> On Monday, 14 October 2024 at 21:00:27 UTC, Derek Fawcus wrote:
>> On Monday, 14 October 2024 at 20:32:08 UTC, Derek Fawcus wrote:
>>> It did however reveal another similar issue with lack of 
>>> access to alloca() from betterC.
>>
>> That alloca issue is:
>>
>> https://issues.dlang.org/show_bug.cgi?id=24815
>
> Thanks for reporting issues. I wonder why you want to use 
> low-level facilities and not D modules (e.g. FixedString)?
>
> SDB at 79

I am evaluating its viability as something added to a large 
multi-threaded time critical C based code base, as a means to add 
some safety, and maybe (eventually) lift to higher abstractions.

Hence it being a case of using betterC, and the parts where it 
should be able to use any C APIs it has offered.

A specific template based implementation of strings is completely 
irrelevant to my evaluating the ability to make use of alloca(), 
or va_copy() - which is how I found the alloca issue. Likewise 
for anything else offered via core.stdc.

The things I've found so far, if presented to colleagues without 
viable workaround would result in use of the betterC subset of D 
simply being a non starter.

Looking in to available third party library packages is simply 
not a consideration at this stage.

DF