Re: Null pointer in __vptr

2021-11-20 Thread Ali Çehreli via Digitalmars-d-learn
On 11/20/21 7:19 AM, frame wrote: > I think this is true for an object instance. But from an interface > instance, the object instance must be accessible somewhere? Everything needed is available from the pointer to a class object (or interface). There are some offset arithmetic involved to

How to make a new dub subpackage? [Answered]

2021-11-20 Thread BoQsc via Digitalmars-d-learn
Note: It is not possible to make subpackage inside subpackage. To make a subpackage with dub; follow these general guidelines. **General guidelines** 1. Create a new folder. 2. Open the folder. 3. Initialise a new package. (`dub init`) 4. Open `dub.json` file * Append this: ```

Re: Null pointer in __vptr

2021-11-20 Thread frame via Digitalmars-d-learn
On Friday, 19 November 2021 at 21:09:16 UTC, Ali Çehreli wrote: I am not sure that's correct. The way I picture it, the code reaches the __vptr by following a pointer; so it's already known. Additionally, I am under the impression that there is only one __vptr for a given type, which all

Re: Dub says that there is an invalid semVer format, but I don't see how.

2021-11-20 Thread Ruby The Roobster via Digitalmars-d-learn
On Saturday, 20 November 2021 at 01:01:05 UTC, rikki cattermole wrote: Don't use ~> for branches. ... Thank you very much. I edited the dub.json, and that fixed the problem(anyways, there is no longer a "testing" branch, so that would have also been an issue.)