Am 18.02.2014 00:17, schrieb Andrew Edwards:
@Sönke Ludwig, please verify that this is fixed and update issue
accordingly: http://d.puremagic.com/issues/show_bug.cgi?id=12137
Confirming the fix. Status has already been updated by Martin Nowak.
A new version of Dgame is ready:
https://github.com/Dgame/Dgame/releases/tag/0.3.2
Don't forget to visit the website and the tutorials:
http://dgame-dev.de/
http://dgame-dev.de/?page=tutorial
Also there is now a Work in Progress section where games are
listed which are written with Dgame:
On Tuesday, 18 February 2014 at 11:56:12 UTC, Namespace wrote:
A new version of Dgame is ready:
https://github.com/Dgame/Dgame/releases/tag/0.3.2
Don't forget to visit the website and the tutorials:
http://dgame-dev.de/
http://dgame-dev.de/?page=tutorial
Also there is now a Work in Progress
On Tuesday, 18 February 2014 at 12:31:04 UTC, simendsjo wrote:
On Tuesday, 18 February 2014 at 11:56:12 UTC, Namespace wrote:
A new version of Dgame is ready:
https://github.com/Dgame/Dgame/releases/tag/0.3.2
Don't forget to visit the website and the tutorials:
http://dgame-dev.de/
Okay so next milestone in Dvorm's[0] development has been meet.
Because of this being technically the first announced release
I'll cover most of it here.
Dvorm is designed to be an ORM heterogeneous of the database
provider itself. I've proven this by using email and MongoDB as
providers.
On Tuesday, 18 February 2014 at 11:56:12 UTC, Namespace wrote:
A new version of Dgame is ready:
https://github.com/Dgame/Dgame/releases/tag/0.3.2
Don't forget to visit the website and the tutorials:
http://dgame-dev.de/
http://dgame-dev.de/?page=tutorial
Also there is now a Work in Progress
On Tuesday, 18 February 2014 at 16:24:56 UTC, Gary Willoughby
wrote:
On Tuesday, 18 February 2014 at 11:56:12 UTC, Namespace wrote:
A new version of Dgame is ready:
https://github.com/Dgame/Dgame/releases/tag/0.3.2
Don't forget to visit the website and the tutorials:
http://dgame-dev.de/
To avoid confusion:
It is not Fedora people who are not willing to help. Problem is with
mirrors.
Imagine personX or companyX decides to become mirror of distribution which
has DMD in their official repository. Before they sync Fedora packages, they
have to ask permissions of all DMD (and
On Mon, 17 Feb 2014 18:17:43 -0500, Andrew Edwards wrote:
First I would like to say thanks to Martin Nowak, Kenji Hara, Jordi
Sayol and Brad Anderson for their support. Their efforts directly impact
my ability to prepare the releases and they work tirelessly to ensure
that it happens.
RC1
On 2/18/2014 10:47 AM, Dejan Lekic wrote:
To avoid confusion:
It is not Fedora people who are not willing to help. Problem is with
mirrors.
Imagine personX or companyX decides to become mirror of distribution which
has DMD in their official repository. Before they sync Fedora packages, they
17-Feb-2014 06:19, Marco Leise пишет:
Am Sun, 09 Feb 2014 12:18:41 +0400
schrieb Dmitry Olshansky dmitry.o...@gmail.com:
09-Feb-2014 09:35, Marco Leise пишет:
Thats neither an improvement over calling validate nor does
that deal with distinguishing between invalid UTF and
Means text is
On 2/18/14, Dmitry Olshansky dmitry.o...@gmail.com wrote:
Well, gedit is a nice example of why just throwing exception is not good
enough for many apps (editors in particular). The fact that it's piece
of junk might be irrelevant ;)
OT: Considering how many big-budget events (World Cup /
On 15 February 2014 20:09, Iain Buclaw ibuc...@gdcproject.org wrote:
On 14 February 2014 19:40, Rainer Schuetze r.sagita...@gmx.de wrote:
I think this is by design to disallow comparison operators and binary
operators in the same expression without paranthesis:
int x = a b c;
Yeah, I
On Tuesday, 18 February 2014 at 06:44:19 UTC, ed wrote:
[snip]
Is your SWIG wrapping online somewhere? - I'd like to take a
look.
https://github.com/lyrebirdsw/vtkdbind
The SWIG bindings were left in a very bad state so they won't
work at the moment. It should generate the D code and
On Monday, 17 February 2014 at 22:58:57 UTC, Andrej Mitrovic
wrote:
And then there are things like trying to allow access to
protected
methods (meaning you have to re-declare them public for the C
wrappers
to access them), which isn't easy because simply re-declaring
them
only works in
On Tuesday, 18 February 2014 at 08:32:07 UTC, ed wrote:
On Tuesday, 18 February 2014 at 06:44:19 UTC, ed wrote:
[snip]
Is your SWIG wrapping online somewhere? - I'd like to take a
look.
https://github.com/lyrebirdsw/vtkdbind
The SWIG bindings were left in a very bad state so they won't
On Tuesday, 18 February 2014 at 09:28:07 UTC, ed wrote:
[snip]
Java -- D is straight forward. It will get interesting though
when things statr compiling :)
s/compiling/linking/
On Tuesday, 18 February 2014 at 09:15:11 UTC, Abdulhaq wrote:
On Tuesday, 18 February 2014 at 08:32:07 UTC, ed wrote:
On Tuesday, 18 February 2014 at 06:44:19 UTC, ed wrote:
[snip]
Is your SWIG wrapping online somewhere? - I'd like to take a
look.
https://github.com/lyrebirdsw/vtkdbind
On Tuesday, 18 February 2014 at 07:45:10 UTC, Paulo Pinto wrote:
It is like traveling back in time when parametric polymorphism
was debated in university papers and everyone was inventing
their own code generation tool.
Back to mid-90's compiler technology when only Ada supported
generics,
On Thursday, 13 February 2014 at 00:06:11 UTC, Brian Schott wrote:
On Thursday, 13 February 2014 at 00:00:11 UTC, Iain Buclaw
wrote:
I'm just curious if anyone else has stumbled onto this, and
whether or not it's just human error on my part. :o)
Regards
Iain.
It's dangerous to go alone.
C++ binding generator is definitely something we will use.
However, I would rather have a good, robust tool that can be used
to generate bindings/wrappers to C libraries. That is of equal
(or even higher I think) importance as C++ binding generator.
On Sunday, 16 February 2014 at 14:10:02 UTC, Abdulhaq wrote:
yes github please.. i'd like to check this out.
OK I'm in the process of migrating the code to github. I was in
such a hurry yesterday evening I didn't list the features
properly:
FEATURES
* All D
* Understandable,
On Tuesday, 18 February 2014 at 11:05:20 UTC, Moritz Maxeiner
wrote:
This looks very nice!
Two questions, though:
1) Is it possible to use an already existing C API with morsel?
The reason I'm asking is, because LLVM classes contain many
methods where an automatic conversion is likely to
On Tuesday, 18 February 2014 at 01:04:10 UTC, simendsjo wrote:
The rejectedsoftware repo is based on an earlier version of
mine which in turn is based on the original by Steve Teale
(britseye).
Thanks for the nod. It's good to see that all those hours were
not wasted.
On 02/18/2014 10:42 AM, logicchains wrote:
I think it makes more sense to attribute the effectiveness of D's
generics implementation to Walter's extensive experience implementing
generics than to attribute it to generics being easy to implement well.
If generics are easy to implement, then why
On Tuesday, 18 February 2014 at 07:45:10 UTC, Paulo Pinto wrote:
It is like traveling back in time when parametric polymorphism
was debated in university papers and everyone was inventing
their own code generation tool.
We are in 2014, not in the early 90's. So to ignore what
happened in
On Tuesday, 11 February 2014 at 19:43:00 UTC, Walter Bright wrote:
The subset would disallow use of any features that rely on:
1. moduleinfo
2. exception handling
3. gc
4. Object
I've used such a subset before when bringing D up on a new
platform, as the new platform didn't have a working
On Tuesday, 18 February 201hanks for the nod. It's good to see
that all those hours were
not wast4 at 11:56:23 UTC, Steve Teale wrote:
On Tuesday, 18 February 2014 at 01:04:10 UTC, simendsjo wrote:
The rejectedsoftware repo is based on an earlier version of
mine which in turn is based on the
On Tuesday, 18 February 2014 at 07:49:20 UTC, Andrej Mitrovic
wrote:
On 2/18/14, Joao Matos j...@tritao.eu wrote:
Nice tools, I've also been working on a C++ binding tool myself
(mostly C#/.NET though).
https://github.com/mono/CppSharp
Does this use Clang's C++ API or libclang which is a C
On Tuesday, 18 February 2014 at 11:52:24 UTC, Abdulhaq wrote:
At the moment smidgen (morsel is the example C++ library I use
for testing) only wraps C++ classes, on the TODO is of course
to wrap C++ top level functions etc. It makes a lot of sense to
add support for C functions too, but to
Travis CI does have Mac boxes, can't you use them?
On Mon, 17 Feb 2014 22:53:15 -0500, Walter Bright
newshou...@digitalmars.com wrote:
On 2/17/2014 6:17 PM, Steven Schveighoffer wrote:
How is this advantageous? It just seems annoying...
Because it makes the programmer's intent clear - are all the cases
accounted for, or are there
On Tuesday, 18 February 2014 at 12:13:56 UTC, Tobias Pankrath
wrote:
I have a hard time to subsume D's type system under parametric
polymorphism, while I see how Javas generics may be. This may
just be way over my head, but I'd rather say D has a
sophisticated way of ad-hoc polymorphism that
On 2/18/14, 11:56 AM, Steven Schveighoffer wrote:
On Mon, 17 Feb 2014 22:53:15 -0500, Walter Bright
newshou...@digitalmars.com wrote:
On 2/17/2014 6:17 PM, Steven Schveighoffer wrote:
How is this advantageous? It just seems annoying...
Because it makes the programmer's intent clear - are
On Tuesday, 18 February 2014 at 12:20:52 UTC, Rel wrote:
So may I ask, what is official decision on the subject? Quite a
lot of people were begging for it for a long time. Obviously
I'd like to have this feature in D because it would finally
allow game, embedded, system (and operating system)
Steven Schveighoffer wrote in message
news:op.xbhfr5kreav7ka@stevens-macbook-pro.local...
Of course, no compiler can make you write correct code. But if you're
going to write a default anyway, odds are you'll choose the right one.
I think your anecdotal experience with exception
On Tue, 18 Feb 2014 11:11:36 -0500, Daniel Murphy
yebbliesnos...@gmail.com wrote:
Steven Schveighoffer wrote in message
news:op.xbhfr5kreav7ka@stevens-macbook-pro.local...
Of course, no compiler can make you write correct code. But if you're
going to write a default anyway, odds are
On Tue, 18 Feb 2014 11:38:41 -0500, Steven Schveighoffer
schvei...@yahoo.com wrote:
The comparison I AM making is that we are implementation a requirement
that will not achieve the behavior goal it sets out to achieve.
*implementing*, not implementation :)
-Steve
On Tuesday, 18 February 2014 at 06:50:36 UTC, logicchains wrote:
Maybe it'd help things if they just directed any inquiries
regarding generics to the most popular preprocessor package?
There are a few around the community. I even wrote a tiny one
myself this morning; it can only handle simple
On Tuesday, 18 February 2014 at 11:56:23 UTC, Steve Teale wrote:
On Tuesday, 18 February 2014 at 01:04:10 UTC, simendsjo wrote:
The rejectedsoftware repo is based on an earlier version of
mine which in turn is based on the original by Steve Teale
(britseye).
Thanks for the nod. It's good
Hey! Thanks everybody for such a quick response. Problem solved!
As Nick and you pointed I didn't understand the build process.
Now, thanks to your video simendsjo, I have new duties. Dub and
Vibed seems worth a detailed look. :-)
I look forward to see the evolution of the mysql native
Steven Schveighoffer wrote in message
news:op.xbhkirppeav7ka@stevens-macbook-pro.local...
My point though, is that the change to require default gains you nothing
except annoyed programmers. Why put it in?
It only gains you nothing if you respond to the error by mindlessly putting
a
On Tuesday, 18 February 2014 at 06:00:25 UTC, Nick Sabalausky
wrote:
Erm, between all of that, plus your strong objection to
default: break;, I really do get the impression you're just
simply being very OCD about this stuff. I don't mean that as an
insult, I just think it's all a bit Adrian
On 02/17/2014 08:04 PM, simendsjo wrote:
I created a video tutorial a couple of days ago that might help you get
started using dub: http://youtu.be/8TV9ZZteYEU
That's helpful, thanks!
Please post it in the D.Announce group too.
On Tuesday, 18 February 2014 at 17:39:58 UTC, John J wrote:
On 02/17/2014 08:04 PM, simendsjo wrote:
I created a video tutorial a couple of days ago that might
help you get
started using dub: http://youtu.be/8TV9ZZteYEU
That's helpful, thanks!
Please post it in the D.Announce group too.
I
On 2/18/14, 2:26 PM, Daniel Murphy wrote:
Steven Schveighoffer wrote in message
news:op.xbhkirppeav7ka@stevens-macbook-pro.local...
My point though, is that the change to require default gains you
nothing except annoyed programmers. Why put it in?
It only gains you nothing if you respond to
On Tue, 18 Feb 2014 12:26:36 -0500, Daniel Murphy
yebbliesnos...@gmail.com wrote:
Steven Schveighoffer wrote in message
news:op.xbhkirppeav7ka@stevens-macbook-pro.local...
My point though, is that the change to require default gains you
nothing except annoyed programmers. Why put it in?
On 2/18/14, 2:52 PM, Steven Schveighoffer wrote:
I think it's the same as saying you have to always have an else clause
after an if statement, even if it's else {}
Lol, I swear I didn't read your answer before posting mine.
Am Tue, 18 Feb 2014 12:14:58 +0400
schrieb Dmitry Olshansky dmitry.o...@gmail.com:
In a sense, \uFFFD means broken encoding.
In a sense yes, in another no. It is a defined code point and
it has a symbol: � a diamond with a question mark inside.
What about lone surrogates?
Those are actual
Am Thu, 13 Feb 2014 00:06:10 +
schrieb Brian Schott briancsch...@gmail.com:
On Thursday, 13 February 2014 at 00:00:11 UTC, Iain Buclaw wrote:
I'm just curious if anyone else has stumbled onto this, and
whether or not it's just human error on my part. :o)
Regards
Iain.
It's
On Tue, 18 Feb 2014 13:18:00 -0500, Marco Leise marco.le...@gmx.de wrote:
Am Thu, 13 Feb 2014 00:06:10 +
schrieb Brian Schott briancsch...@gmail.com:
On Thursday, 13 February 2014 at 00:00:11 UTC, Iain Buclaw wrote:
I'm just curious if anyone else has stumbled onto this, and
whether or
On Sunday, 16 February 2014 at 15:43:31 UTC, Manu wrote:
1.
case fall-through is not supported;
goto case; automagically goes to the next case.
2.
'case 1, 3, 7, 8:' is awesome! ...but ranged cases have a
totally different
syntax: 'case 1: .. case 3:'
Why settle on that syntax? The
On 2014-02-18 03:16, Daniel Murphy wrote:
That would be a runtime use of 'foo', to get the function pointer.
Other modules can get the function pointer as well. Or perhaps that's
what you're saying.
--
/Jacob Carlborg
On Monday, 17 February 2014 at 20:00:18 UTC, Paulo Pinto wrote:
You have provided a very nice answer.
The problem with Go generics is religious, I might have to eat
my own words, but I seriously doubt they will ever support it.
They are too focused with Java and C++ as models, to accept
What's the best solution to communicate between threads in D
today if I care about
1. Security Correctness?
2. Performance?
and are these mutually exclusive?
Does Phobos or other library contain lockfree queues?
From what I can see std.concurrent.MessageBox requires
Mutex-locking. Is this
On Tuesday, 18 February 2014 at 21:05:38 UTC, Nordlöw wrote:
What's the best solution to communicate between threads in D
today if I care about
1. Security Correctness?
2. Performance?
and are these mutually exclusive?
Does Phobos or other library contain lockfree queues?
From what I can
On Tuesday, 18 February 2014 at 21:05:38 UTC, Nordlöw wrote:
What's the best solution to communicate between threads in D
today if I care about
1. Security Correctness?
2. Performance?
and are these mutually exclusive?
Does Phobos or other library contain lockfree queues?
From what I can
On Tuesday, 18 February 2014 at 21:21:54 UTC, deadalnix wrote:
On Tuesday, 18 February 2014 at 21:05:38 UTC, Nordlöw wrote:
What's the best solution to communicate between threads in D
today if I care about
1. Security Correctness?
2. Performance?
and are these mutually exclusive?
Does
I have no experience in writing threadlocking queues.
I of course mean lock-free queues.
/Per
On 2/18/2014 7:45 AM, Ary Borenszweig wrote:
I think that final switch should have the function of checking that you
covered all cases,
That's just what it does.
be it with a default case or not.
final is meaningless with a default.
On 2/18/2014 8:38 AM, Steven Schveighoffer wrote:
My point though, is that the change to require default gains you nothing except
annoyed programmers. Why put it in?
This was fiercely debated at length and settled here years ago. It isn't going
to change.
The comparison I AM making is
On Tuesday, 18 February 2014 at 21:37:09 UTC, Nordlöw wrote:
On Tuesday, 18 February 2014 at 21:21:54 UTC, deadalnix wrote:
On Tuesday, 18 February 2014 at 21:05:38 UTC, Nordlöw wrote:
What's the best solution to communicate between threads in D
today if I care about
1. Security
http://cacm.acm.org/magazines/2014/2/171689-mars-code/fulltext
Some interesting tidbits:
We later revised it to require that the flight software as a whole, and each
module within it, had to reach a minimal assertion density of 2%. There is
compelling evidence that higher assertion densities
On 2/19/14, 12:20 AM, Nordlöw wrote:
I have no experience in writing threadlocking queues.
I of course mean lock-free queues.
/Per
std.allocator has one.
Andrei
On Tuesday, 18 February 2014 at 23:05:21 UTC, Walter Bright wrote:
http://cacm.acm.org/magazines/2014/2/171689-mars-code/fulltext
Some interesting tidbits:
We later revised it to require that the flight software as a
whole, and each module within it, had to reach a minimal
assertion density
On Tuesday, 18 February 2014 at 23:05:21 UTC, Walter Bright wrote:
http://cacm.acm.org/magazines/2014/2/171689-mars-code/fulltext
Some interesting tidbits:
We later revised it to require that the flight software as a
whole, and each module within it, had to reach a minimal
assertion density
On Tuesday, 18 February 2014 at 23:45:37 UTC, Andrei Alexandrescu
wrote:
On 2/19/14, 12:20 AM, Nordlöw wrote:
I have no experience in writing threadlocking queues.
I of course mean lock-free queues.
/Per
std.allocator has one.
Andrei
I'd say upcoming std.allocator will have one. It's
On Wednesday, 19 February 2014 at 00:16:03 UTC, Tolga Cakiroglu
wrote:
TL;DR the link though, how are they detecting that a CPU fails?
An information must be passes outside of CPU to do this. The
only solution comes to my mind is that main CPU changes a
variable on an external memory at
On Tuesday, 18 February 2014 at 21:37:09 UTC, Nordlöw wrote:
On Tuesday, 18 February 2014 at 21:21:54 UTC, deadalnix wrote:
On Tuesday, 18 February 2014 at 21:05:38 UTC, Nordlöw wrote:
What's the best solution to communicate between threads in D
today if I care about
1. Security
I am using D epoll on Fedora 3.12.10-300.fc20.x86_64 and am
running into a very odd issue.
The data.ptr value of the epoll_event struct when it comes back
from the epoll_wait call seems to have lost the top 32 bits.
GDB session produced the following:
Before epoll
$3 = {events = 1, data =
On Wednesday, 19 February 2014 at 02:39:39 UTC, sumo wrote:
I am using D epoll on Fedora 3.12.10-300.fc20.x86_64 and am
running into a very odd issue.
For giggles the D kevent version on FreeBSD has no problems
(80079af00 is pointer to the event object):
Before kevent:
0x800799f40:
If travis ci can query and interact with my build coordinator, then
maybe, but I'm pretty sure the answer is it can't. And, if it can I
doubt they're willing to dedicate one of their boxes to my test fleet,
which is what I need. The test fleet is busy 24/7 and almost never
catches up and
On 02/18/2014 12:46 PM, simendsjo wrote:
I've created two more videos, but they are pure live-coding D basics and
probably of less interest to most of the users here:
https://www.youtube.com/playlist?list=PLqABwcsDQUo59iBOM5DFtqbwrMhL4PWcQ
I expect there will be made an announcement about that
On Wednesday, 19 February 2014 at 01:09:43 UTC, Xinok wrote:
On Wednesday, 19 February 2014 at 00:16:03 UTC, Tolga Cakiroglu
wrote:
TL;DR the link though, how are they detecting that a CPU
fails? An information must be passes outside of CPU to do
this. The only solution comes to my mind is
On Tuesday, 18 February 2014 at 07:50:23 UTC, bearophile wrote:
Stanislav Blinov:
http://dpaste.dzfl.pl/9d7feeab59f6
Few small things should still be improved, but it's an
improvement. Perhaps it needs to use a reference counting from
Phobos.
COW for matrices? Aw, come on... :)
LDC
None of your buffers are on stack in both examples. As those are
dynamic arrays you only get pointer + length as value and data
itself resides on heap in some unknown location. It can be in
cache too, of course, if it has been used actively, but it can't
be verified based on this simple
On Tuesday, 18 February 2014 at 07:45:18 UTC, bearophile wrote:
Stanislav Blinov:
that explicit ctor
for Dimension is completely unnecessary too.
I like a constructor(s) like that because it catches bugs like:
auto d = Dimension(5);
Hmmm... yeah, ok, not completely unnecessary :)
I am testing with the import expression. I am using the -J flag
while compiling.
dmd app.d -J/home/user/include
void main(){
auto test = json.parseJSON(
import(/home/user/include/test.json) );
}
1. Because I am giving the full path of that file to be imported.
But compiler is
On Tuesday, 18 February 2014 at 05:21:24 UTC, Brian Schott wrote:
On Monday, 17 February 2014 at 19:22:38 UTC, simendsjo wrote:
Should the following two uses be a compile-time error?
foreach(i; 10 .. 0) // Never executes
foreach(i; iota(10, 0)) // .. neither does this
I would like the
On Tuesday, 18 February 2014 at 08:45:16 UTC, Tolga Cakiroglu
(tcak) wrote:
I am testing with the import expression. I am using the -J
flag while compiling.
dmd app.d -J/home/user/include
void main(){
auto test = json.parseJSON(
import(/home/user/include/test.json) );
}
1. Because I am
Stanislav Blinov:
allocationTest ...
Time required: 1 sec, 112 ms, 827 μs, and 3 hnsecs
multiplicationTest ...
Time required: 1 sec, 234 ms, 417 μs, and 8 hnsecs
Physics teaches us that those experimental measures are expressed
with a excessive precision. For such benchmarks
Stanislav Blinov:
LDC yields roughly the same times.
This is surprising.
To me as well. I haven't yet tried to dig deep though.
I have compiled your code with (a single module, 32 bit Windows):
dmd -wi -vcolumns -O -release -inline -noboundscheck matrix3.d
ldmd2 -wi -O -release -inline
On Tuesday, 18 February 2014 at 08:50:23 UTC, bearophile wrote:
Stanislav Blinov:
LDC yields roughly the same times.
This is surprising.
To me as well. I haven't yet tried to dig deep though.
I have compiled your code with (a single module, 32 bit
Windows):
dmd -wi -vcolumns -O
Tolga Cakiroglu (tcak):
1. Because I am giving the full path of that file to be
imported, compiler is complaining about that it cannot find
the file. If I remove the path, and leave the file name only,
it works. Am I doing something wrong, or bug?
2. Why do I need to tell compiler where to
On Tuesday, 18 February 2014 at 08:45:16 UTC, Tolga Cakiroglu
(tcak) wrote:
1. Because I am giving the full path of that file to be
imported. But compiler is complaining about that it cannot find
the file. If I remove the path, and leave the file name only,
it works. Am I doing something
Per Nordlöw:
Why isn't equality == operator used here instead?
In some cases I'd even like to use ~ instead of chain().
Bye,
bearophile
On Tuesday, 18 February 2014 at 09:31:55 UTC, Per Nordlöw wrote:
I'm curious to why we need std.range.equal in cases such as
bool isPalindrome(Range)(in Range range) if
(isBidirectionalRange!Range)
{
return range.retro.equal(range);
}
Why isn't equality == operator used here instead?
On Tuesday, 18 February 2014 at 09:34:41 UTC, bearophile wrote:
In some cases I'd even like to use ~ instead of chain().
Range interface should be minimal. Don't forget that user types
can provide range interface and still benefit from operator
overloading for different purposes.
I have written a module as below:
file: lib.d
import core.sys.posix.dlfcn;
private static this(){}
private static ~this(){}
public shared class Apps{
}
---
This code is compiled with -H flag to generate an interface
file. Generated interface file is below:
file: lib.di
// D import
On Tuesday, 18 February 2014 at 09:24:50 UTC, Dicebot wrote:
On Tuesday, 18 February 2014 at 08:45:16 UTC, Tolga Cakiroglu
(tcak) wrote:
1. Because I am giving the full path of that file to be
imported. But compiler is complaining about that it cannot
find the file. If I remove the path, and
On Tuesday, 18 February 2014 at 10:07:37 UTC, Tolga Cakiroglu
(tcak) wrote:
Bug?
Yup.
(I don't know if I should immediately file a bug when I think
it is a bug without asking what other people thinks.)
1) Do a seach in bugzilla
2) If the search doesn't show anything similar, file it
3)
On Tuesday, 18 February 2014 at 10:10:14 UTC, Tolga Cakiroglu
wrote:
Hmm. Should I understand the sandbox as if I am going to be
compiling someone else's code, only looking at -J flags will be
enough to make sure it is not using any of my private files?
It is the intention. I can't guarantee
...And if I define opEquals as it was made by Robin, i.e. like
this:
bool opEquals(ref const Matrix other) const pure nothrow {
version (all) {
if (dim != other.dim) return false;
foreach(immutable i, const ref e; data)
if (e != other.data[i])
/home/alaran/tmp/test.d(5:16)[warn]: 3 is larger than 2. This
slice is likely incorrect.
/home/alaran/tmp/test.d(6:22)[warn]: 20 is larger than 10. Did
you mean to use 'foreach_reverse( ... ; 10 .. 20)'?
Isn't foreach_reverse being deprecated?
Oh. If so, what would be the right way to
Sergei Nosov:
Isn't foreach_reverse being deprecated?
The idea was discussed a little, but it's not deprecated, and
probably it will not be deprecated.
Bye,
bearophile
On Tuesday, 18 February 2014 at 10:15:51 UTC, Stanislav Blinov
wrote:
On Tuesday, 18 February 2014 at 10:07:37 UTC, Tolga Cakiroglu
(tcak) wrote:
Bug?
Yup.
(I don't know if I should immediately file a bug when I think
it is a bug without asking what other people thinks.)
1) Do a seach
Stanislav Blinov:
Range interface should be minimal.
I agree. But I didn't mean to ask for that operator in the Range
protocol. I think some ranges should define a ~ operator. It's
easy to write a chainable trait. I did that for my nonstandard
D1 library.
Bye,
bearophile
Rather than change it to int/ulong, just change it to 'size_t
len = parent.children.length+1' (or auto instead of size_t).
This way it's proper for both 32-bit and 64-bit and you don't
need to worry about architecture. If you do need a signed
version, you can use ptrdiff_t.
Yup, that's what
On Tuesday, 18 February 2014 at 10:47:33 UTC, bearophile wrote:
Stanislav Blinov:
Range interface should be minimal.
I agree. But I didn't mean to ask for that operator in the
Range protocol. I think some ranges should define a ~ operator.
It's easy to write a chainable trait. I did that
On Tuesday, 18 February 2014 at 11:39:12 UTC, Per Nordlöw wrote:
On Tuesday, 18 February 2014 at 10:47:33 UTC, bearophile wrote:
Stanislav Blinov:
Range interface should be minimal.
I agree. But I didn't mean to ask for that operator in the
Range protocol. I think some ranges should define
1 - 100 of 186 matches
Mail list logo
