On Saturday, September 2, 2023 4:38:41 AM BST confused via Digitalmars-d-learn wrote:
> On Friday, 1 September 2023 at 13:45:05 UTC, evilrat wrote:
> > It is shadowing default implicit "import object;", here a demonstration
> >
> > ```d
> > // this example shows default implicit import of "object" module
> > // compile this example:
> > //   ldc2 -c test.d
> > // output:
> > //   tuple("object", "core", "main", "thisModule")
> >
> > // just a random import
> > import core.stdc.stdio;
> >
> > void main() { }
> >
> > alias thisModule = __traits(parent, main);
> > pragma(msg,  __traits(allMembers, thisModule)); // has
> > implicitly imported 'object' module
> > ```
>
> Is there no way for the two to coexist?

If you put it into a package, then you could have your own object module that then isn't at the top level - e.g. mypkg/object.d with

module mypkg.object;

but you can't have more than one module in your program with the same full module name. So, in the case of the top-level module, object, you can only declare your own if you replace the default one, which you might do in some special situations, but it's not something that you would normally do, and you can never have both the normal object module and your own in the same program.

- Jonathan M Davis

On Saturday, 2 September 2023 at 07:59:31 UTC, Jonathan M Davis wrote:
> If you put it into a package, then you could have your own object module that then isn't at the top level - e.g. mypkg/object.d with
>
> module mypkg.object;
>
> but you can't have more than one module in your program with the same full module name. So, in the case of the top-level module, object, you can only declare your own if you replace the default one, which you might do in some special situations, but it's not something that you would normally do, and you can never have both the normal object module and your own in the same program.
>
> - Jonathan M Davis

So then I guess I'd still like to know how I'm expected to store and access an array of characters without the C runtime as I tried in my original post.

On Monday, 4 September 2023 at 07:39:21 UTC, confused wrote:
>
> So then I guess I'd still like to know how I'm expected to store and access an array of characters without the C runtime as I tried in my original post.

Without C runtime functions such as malloc you can still have fixed-length arrays, for string variables the compiler will emit null-terminated string at compile time in cases like that making it compatible with C functions.

Note that it not the case for other string operations like concat operator (is it available in betterC?), in that case if you want to pass the resulting string you have to add null terminator by hand.

If you need to allocate memory at runtime and still wan't to avoid C runtime, well I guess you have to do some syscalls then...
Or use another allocator library, jmalloc maybe? Though I don't have the experience with them and don't know if they are using C runtime somewhere inside or handle that low level OS/syscalls stuff by itself.