Linking...
ld: warning: pointer not aligned at address 0x10017A4C9
(_D30TypeInfo_AxS3std4file8DirEntry6__initZ + 16 from
.dub/build/application-debug-posix.osx-x86_64-dmd_2072-EFDCDF4D45F944F7A9B1AEA5C32F81ED/spellit.o)
...
and this goes on forever!
30.03.2017 21:59, H. S. Teoh via Digitalmars-d-learn пишет:
http://wiki.dlang.org/User:Quickfur/Compile-time_vs._compile-time
Really useful link, thank you very much!
Dne 31.3.2017 v 00:41 Inquie via Digitalmars-d-learn napsal(a):
Is there a 64-bit DMD compiler that doesn't have the 2GB memory
limitations that the 32-bit one has? I am not talking about compiling
64-bit programs but the dmd binary itself.
I belive it is 4GB ok maybe 3GB :)
Is there a 64-bit DMD compiler that doesn't have the 2GB memory
limitations that the 32-bit one has? I am not talking about
compiling 64-bit programs but the dmd binary itself.
On Thu, Mar 30, 2017 at 06:21:43PM +, Enigma via Digitalmars-d-learn wrote:
> Is it possible to compute at compile time computations on a manifest
> constant that contains values(in a somewhat complex way, but that
> shouldn't matter)?
Yes, see below.
> I am using foreach and it seems to be
On 03/30/2017 11:21 AM, Enigma wrote:
> Is it possible to compute at compile time computations on a manifest
> constant that contains values(in a somewhat complex way, but that
> shouldn't matter)?
You can do anything that you want as long as it's available at compile
time. For example, you
On Thursday, 30 March 2017 at 18:21:43 UTC, Enigma wrote:
I am using foreach and it seems to be done dynamically as I can
step through the code for each value and see them change. This
tells me it is not done at compile time like it should be.
Remember two facts:
1) CTFE is never done unless
Is it possible to compute at compile time computations on a
manifest constant that contains values(in a somewhat complex way,
but that shouldn't matter)?
I am using foreach and it seems to be done dynamically as I can
step through the code for each value and see them change. This
tells me it
On Thursday, 30 March 2017 at 11:22:05 UTC, Gary Willoughby wrote:
On Wednesday, 29 March 2017 at 19:19:48 UTC, Enigma wrote:
I have a memory buffer allocated using different methods. It
is simply a pointer and a size.
I would like to be able to manage this buffer by treating it
as a memory
On Wednesday, 29 March 2017 at 23:26:04 UTC, H. S. Teoh wrote:
On Wed, Mar 29, 2017 at 11:01:12PM +, Enigma via
Digitalmars-d-learn wrote:
On Wednesday, 29 March 2017 at 21:36:14 UTC, Petar Kirov
[ZombineDev] wrote:
> [...]
But these seem to require passing a mallocator. I simply want
to
On Wednesday, 29 March 2017 at 10:08:02 UTC, abad wrote:
Related question, it seems that final methods are allowed in
interfaces. Obviously you can't implement them anywhere, so is
this also on purpose and on what rationale? :)
That is not necessarily true. Final doesn't imply it can't be
On Wednesday, 29 March 2017 at 19:19:48 UTC, Enigma wrote:
I have a memory buffer allocated using different methods. It is
simply a pointer and a size.
I would like to be able to manage this buffer by treating it as
a memory pool or heap. I think I can use allocators to do this
but not sure
On Wednesday, 29 March 2017 at 09:50:10 UTC, abad wrote:
Is this on purpose and what's the rationale?
In Andrei's book, chapter 6.9.1 "the non virtual interface (NVI)
idiom" answers your question. It cites this article by Herb
Sutter as the originator of the idea:
13 matches
Mail list logo
