On Fri, 2014-07-04 at 12:48 +, via Digitalmars-d wrote:
[…]
> I pick the most stable tool for the job. Meaning I usually end up
> with C, conservative use of C++, Python 2.7, Javascript, SQL or
[…]
That should, of course, have read Python 3.4!
--
Russel.
===
On Fri, 2014-07-04 at 20:25 +, Chris Cain via Digitalmars-d wrote:
[…]
> The big problem with that is "C++ style memory management"
> implies we're going to have new/delete which AFAIK delete is
> depreciated and new is currently hardcoded to use the GC.
[…]
All the C++ folk are saying that
I don’t think that any k'i't'c'h'e'n company can compete with
K'i't'c'h'e'n
'D'e's'i'g'n Lancashire .
On Friday, 4 July 2014 at 01:17:39 UTC, Brad Anderson wrote:
Just the D and moons:
https://drive.google.com/file/d/0Bx3n3LnLsNBzN1didmlWZmtQQTQ/edit?usp=sharing
They show up as pixilated in the Google Drive preview because
they are being rendered at the specified page size of 125x125px
but they
On Thu, 3 Jul 2014 14:01:23 -0700
Jonathan M Davis via Digitalmars-d wrote:
> I'm fine with real varying from platform to platform depending on
> what makes sense for that platform, but I think that it should be
> clear what real is generally supposed to be (e.g. the largest
> floating point type
On Friday, 4 July 2014 at 21:08:27 UTC, Walter Bright wrote:
rewriting what C++ "best practices" are. To characterize all
this churn as "stablility" is awfully charitable.
Pfft, a lot of performance C++ code is roughly in 1998 land
without exceptions and rtti.
Uh-huh. And how much profession
On Friday, 4 July 2014 at 21:09:05 UTC, Remo wrote:
By "C++ style memory management" I do not mean naked new/delete
or malloc/free.
What I mean is RAII, smart pointers and destructor's.
What is the proper replacement for std::unique_ptr and
std::shared_ptr in D2 ?
Of course with move support f
On 7/4/2014 1:41 PM, "Ola Fosheim Grøstad"
" wrote:
On Friday, 4 July 2014 at 20:28:36 UTC, Walter Bright wrote:
There's no such thing as done for a working language. C++, for example, is
constantly in flux. Every release by every vendor alters which parts of the
standard and draft standard it s
On Friday, 4 July 2014 at 20:43:01 UTC, Dicebot wrote:
On Friday, 4 July 2014 at 20:25:24 UTC, Chris Cain wrote:
On Friday, 4 July 2014 at 19:46:40 UTC, Remo wrote:
Who want to use C-style memory management today ?
How about C++ style memory management, is this easy to this
in D2
now ?
The
At 1000$ this will find a hacker in no time.
On Friday, July 4, 2014, Walter Bright via Digitalmars-d <
digitalmars-d@puremagic.com> wrote:
> On 7/4/2014 5:49 AM, Andrej Mitrovic via Digitalmars-d wrote:
>>
>> Now *that* I definitely cannot work on. It's a complete conflict of
>> interest due to o
05-Jul-2014 00:25, Chris Cain пишет:
On Friday, 4 July 2014 at 19:46:40 UTC, Remo wrote:
Who want to use C-style memory management today ?
How about C++ style memory management, is this easy to this in D2
now ?
The big problem with that is "C++ style memory management" implies we're
going to h
On Friday, 4 July 2014 at 20:25:24 UTC, Chris Cain wrote:
On Friday, 4 July 2014 at 19:46:40 UTC, Remo wrote:
Who want to use C-style memory management today ?
How about C++ style memory management, is this easy to this in
D2
now ?
The big problem with that is "C++ style memory management"
On Friday, 4 July 2014 at 20:28:36 UTC, Walter Bright wrote:
There's no such thing as done for a working language. C++, for
example, is constantly in flux. Every release by every vendor
alters which parts of the standard and draft standard it
supports.
And no sane devs rely on those experimen
On 7/4/2014 5:49 AM, Andrej Mitrovic via Digitalmars-d wrote:
Now *that* I definitely cannot work on. It's a complete conflict of
interest due to our two companies. :)
Dang, we can't afford any mutiny on the bounty!
On Friday, 4 July 2014 at 20:25:24 UTC, Chris Cain wrote:
depreciated
deprecated*. I swear I say it correctly and when I'm coding I
type it correctly there XD
On Friday, 4 July 2014 at 19:46:40 UTC, Remo wrote:
Who want to use C-style memory management today ?
How about C++ style memory management, is this easy to this in
D2
now ?
The big problem with that is "C++ style memory management"
implies we're going to have new/delete which AFAIK delete i
On 7/4/2014 1:13 PM, "Ola Fosheim Grøstad"
" wrote:
If you can commit to a spec for D2 that is final, then you can also plan for
when D2 is done.
There's no such thing as done for a working language. C++, for example, is
constantly in flux. Every release by every vendor alters which parts of t
On Friday, 4 July 2014 at 19:53:11 UTC, Walter Bright wrote:
I'm curious how that would affect anyone currently using
dmd/gdc/ldc in getting professional work done.
It doesn't affect them since they are on x86 (until they want to
use co-processor auto-vectorization). As far as I can tell, also
On 7/4/2014 12:07 PM, "Ola Fosheim Grøstad"
" wrote:
The D spec should be clear on what IEEE 754 compliance actually
means and relate it to all probable scenarios.
I'm curious how that would affect anyone currently using dmd/gdc/ldc in getting
professional work done.
On Friday, 4 July 2014 at 16:16:35 UTC, Meta wrote:
On Friday, 4 July 2014 at 15:29:06 UTC, Brian Rogoff wrote:
On Friday, 4 July 2014 at 14:10:29 UTC, bearophile wrote:
D: y u no distinguish between ints/longs/floats/doubles and
pointers when taking out the trash? You argue that internal
poin
On Friday, 4 July 2014 at 19:13:28 UTC, Igor wrote:
Hello,
I want to represent a tree node in D. I think if struct works
for it:
struct Node {
Node* l, r;
}
But can I use pointers? Will GC treat them properly? I'm
leaning to think it should be okay.
Yes, in fact that's how it's done in pho
Hello,
I want to represent a tree node in D. I think if struct works for
it:
struct Node {
Node* l, r;
}
But can I use pointers? Will GC treat them properly? I'm leaning
to think it should be okay.
On Friday, 4 July 2014 at 12:59:41 UTC, bearophile wrote:
If the D maintainers don't care about reaching a stable state,
at the expense of scope and features,
Don't be silly, D devs care a lot about reaching stability,
fixing bugs, etc.
But not to the extent that they are willing to limit th
On Friday, 4 July 2014 at 14:47:12 UTC, Chris Cain wrote:
If GC.enable and GC.disable truly disallowed GC running (or
alternative `GC.hard_disable`/`GC.hard_enable` existed that
guaranteed such) then you could use that to make sure that the
GC didn't collect in the middle of a pair of those c
On 7/4/2014 10:42 AM, John Colvin wrote:
Who are these "compiler implementers"?
Whoever decides to implement D for a particular platform.
Are you actually suggesting that, for example, ldc and gdc would seperately
decide
I am confident they will exercise good judgement in making their imp
On Friday, 4 July 2014 at 17:05:16 UTC, Walter Bright wrote:
On 7/4/2014 3:38 AM, Don wrote:
What is "the longest type supported by the native hardware"? I
don't know what
that means, and I don't think it even makes sense.
Most of the time, it is quite clear.
For example, Sparc has 128-bit
On 7/4/2014 6:01 AM, Daniel Murphy wrote:
long double may not be the same size as D's real, eg in msvc it's 64-bit. You
can still still call these functions from D using double in C, but the mangling
will not match in C++.
You are correct in that VC++ mangles double as 'N' and long double as '
On 7/4/2014 3:38 AM, Don wrote:
What is "the longest type supported by the native hardware"? I don't know what
that means, and I don't think it even makes sense.
Most of the time, it is quite clear.
For example, Sparc has 128-bit quads, but they only have partial support.
Effectively. they a
On Friday, 4 July 2014 at 14:47:12 UTC, Chris Cain wrote:
Is there a way to lock the GC currently?
There are critical regions in core.thread. While in such a
region, your thread will never be suspended, effectively also
precluding the GC from running. They are a rather dangerous tool
though,
On 7/4/2014 5:06 AM, Daniel Murphy wrote:
"Walter Bright" wrote in message news:lp26l3$qlk$1...@digitalmars.com...
Per the D spec, 'real' will be the longest type supported by the native
hardware.
So if you were targeting a processor with only soft-float real would be
undefined? Fixing the
On 7/4/2014 5:48 AM, "Ola Fosheim Grøstad"
" wrote:
I pick the most stable tool for the job. Meaning I usually end up with C,
conservative use of C++, Python 2.7, Javascript, SQL or XSLT… :-P Rarely D and
occasionally Dart (which isn't particularly stable either and is rejected
beacuase of it) an
On 7/4/2014 1:37 AM, Max Samukha wrote:
On Friday, 4 July 2014 at 01:26:37 UTC, Walter Bright wrote:
If you sit around waiting for arbitrary perfection, you'll never get any work
done. I don't care that my truck has dings in it, either, it's a truck and
it's useful for what I need it for :-)
On 4 July 2014 17:31, Daniel Murphy via Digitalmars-d
wrote:
> "Iain Buclaw via Digitalmars-d" wrote in message
> news:mailman.3268.1404486824.2907.digitalmar...@puremagic.com...
>
>
>> You're confusing long double with size_t. I did a cursory look up
>> msvc++ mangling, and long double is alway
"Iain Buclaw via Digitalmars-d" wrote in message
news:mailman.3268.1404486824.2907.digitalmar...@puremagic.com...
You're confusing long double with size_t. I did a cursory look up
msvc++ mangling, and long double is always 'O'. The itanium spec says
that long double is 'e' - unless 128bits i
I was delighted when the kitchen arrived and was very impressed
with the service Stilhaus Kitchens gave me. They've certainly got
a contented customer in me and everyone in my house loves our new
elegant kitchen.
http://www.stilhauskitchens1.co.uk
On Friday, 4 July 2014 at 15:29:06 UTC, Brian Rogoff wrote:
On Friday, 4 July 2014 at 14:10:29 UTC, bearophile wrote:
D: y u no distinguish between ints/longs/floats/doubles and
pointers when taking out the trash? You argue that internal
pointers make implementing a precise garbage collector (w
I was delighted when the kitchen arrived and was very impressed
with the service Stilhaus Kitchens gave me. They've certainly got
a contented customer in me and everyone in my house loves our new
elegant kitchen.
[URL=http://www.stilhauskitchens1.co.uk]Stilhaus Kitchens
Reviews[/URL]
On Friday, 4 July 2014 at 14:10:29 UTC, bearophile wrote:
D: y u no distinguish between ints/longs/floats/doubles and
pointers when taking out the trash? You argue that internal
pointers make implementing a precise garbage collector (which
wouldn’t mistake numbers for pointers) impossible, but
On 4 July 2014 14:01, Daniel Murphy via Digitalmars-d
wrote:
>
> "Iain Buclaw via Digitalmars-d" wrote in
> message news:mailman.3265.1404477916.2907.digitalmar...@puremagic.com...
>
>
>> FP types are fixed. float is 32bit, double 64bit.
>
>
> That's 2/3.
>
>
>> What 's the mangling problem with
On Friday, 4 July 2014 at 10:36:03 UTC, safety0ff wrote:
I just thought a little more about this and you will always
have a race.
Consider this code:
auto a = malloc(aSize);
GC.addRange(a, aSize);
auto b = realloc(a, aSize * 2);
If realloc moves the data (a != b) and the GC runs before you
ca
Go (compared to several other languages) for servers:
http://togototo.wordpress.com/2014/07/04/why-go-is-great-for-servers/
http://www.reddit.com/r/programming/comments/29t3zy/why_go_is_great_for_servers/
The two comments about D:
I considered an implementation in D, but while D has green
thr
"Iain Buclaw via Digitalmars-d" wrote in
message news:mailman.3265.1404477916.2907.digitalmar...@puremagic.com...
FP types are fixed. float is 32bit, double 64bit.
That's 2/3.
What 's the mangling problem with long double? There's only *one* long
double.
long double may not be the sam
Ola Fosheim Grøstad:
If the D maintainers don't care about reaching a stable state,
at the expense of scope and features,
Don't be silly, D devs care a lot about reaching stability,
fixing bugs, etc.
Bye,
bearophile
On Friday, 4 July 2014 at 00:11:25 UTC, Brad Anderson wrote:
I've had this .svg of the flat version of the logo around for a
few years that is a bit cleaner than the one you quickly put
together (sharper edges, and I think your bottom is truncated a
bit).
I didn't put it together quickly, but r
On 7/3/14, Benoit Rostykus via Digitalmars-d
wrote:
> We just set up a significant bounty for this bug:
> https://www.bountysource.com/issues/2900969-struct-destructors-are-not-called-by-the-gc-but-called-on-explicit-delete
Now *that* I definitely cannot work on. It's a complete conflict of
inter
On Friday, 4 July 2014 at 01:26:37 UTC, Walter Bright wrote:
The issues you presented are subjective and a matter of opinion.
Well, one has to agree on a definition for a start! :)
If you sit around waiting for arbitrary perfection, you'll
never get any work done.
I pick the most stable too
On 4 Jul 2014 13:10, "Daniel Murphy via Digitalmars-d" <
digitalmars-d@puremagic.com> wrote:
>
> "Walter Bright" wrote in message news:lp26l3$qlk$1...@digitalmars.com...
>
>
>> Per the D spec, 'real' will be the longest type supported by the native
hardware.
>
>
> So if you were targeting a proces
On Thursday, 3 July 2014 at 21:57:14 UTC, Benoit Rostykus wrote:
We just set up a significant bounty for this bug:
https://www.bountysource.com/issues/2900969-struct-destructors-are-not-called-by-the-gc-but-called-on-explicit-delete
However, it is referenced on BountySource under the "DLang's
Is
"Wanderer" wrote in message news:aroorrxjloihxtthk...@forum.dlang.org...
Databases don't sort their records physically. The main reason
for that is that each record has many columns so there are many
various possible sort orders.
Yes they do. http://en.wikipedia.org/wiki/Database_index#Clus
"Walter Bright" wrote in message news:lp26l3$qlk$1...@digitalmars.com...
Per the D spec, 'real' will be the longest type supported by the native
hardware.
So if you were targeting a processor with only soft-float real would be
undefined? Fixing the widths of the integers was a great idea, a
On Friday, 4 July 2014 at 08:21:05 UTC, chmike wrote:
Unfortunately I wasn't able to compile and run the hello world
program because the build command used by default is
make -debug -g -m64 -ofbin/debug/testQtCreatorD -odobj/debug
testQtCreatorD.d
So I'm not sure I properly installed everyth
On 4 Jul 2014 10:40, "Joseph Rushton Wakeling via Digitalmars-d" <
digitalmars-d@puremagic.com> wrote:
>
> On Thursday, 3 July 2014 at 14:26:51 UTC, Iain Buclaw via Digitalmars-d
wrote:
>>
>> It's also a handy coincidence that for many platforms the targets
>> largest supported FP and *double* type
On 4 Jul 2014 08:40, "Russel Winder via Digitalmars-d" <
digitalmars-d@puremagic.com> wrote:
>
> On Fri, 2014-07-04 at 07:46 +0100, Iain Buclaw via Digitalmars-d wrote:
> […]
> > Powered by Martian Technology
>
> @SarcasticRover is telling us "Do not come to Mars." Perhaps its
> commentary need cen
If you reallocate doubling the size, it's likely such reallocs
always move, so they should be equivalent to malloc+free, so your
code can be
mem2 = alloc(sz*2);
mem2[] = mem1[];
addRange(mem2);
removeRange(mem1);
free(mem1);
if not, you need to lock the GC so that it won't interfere during
re
On Thursday, 3 July 2014 at 21:53:25 UTC, Brian Schott wrote:
I think that the only sane way to solve this is to define in
the specs for core.memory that GC.addRange will only ever store
one entry per pointer, and that the length will be the value of
"sz" from the most recent call to addRange
On Thursday, 3 July 2014 at 00:03:47 UTC, Walter Bright wrote:
On 7/2/2014 3:15 PM, Sean Kelly wrote:
On Wednesday, 2 July 2014 at 21:44:17 UTC, Walter Bright wrote:
C long double == D real for 32 and 64 bit OSX, Linux, and
FreeBSD.
And it's 'double double' on PPC and 128 bit quad on SPARC.
A
On Thursday, 3 July 2014 at 14:26:51 UTC, Iain Buclaw via
Digitalmars-d wrote:
It's also a handy coincidence that for many platforms the
targets
largest supported FP and *double* type happen to be the same
too.
Out of curiosity, how is C "long double" interpreted on those
platforms? Just doe
On Friday, 4 July 2014 at 01:26:37 UTC, Walter Bright wrote:
If you sit around waiting for arbitrary perfection, you'll
never get any work done. I don't care that my truck has dings
in it, either, it's a truck and it's useful for what I need it
for :-)
Even though a Tesla is of no more use
Thank you very much. I was able to compile the plugins.
But I failed compiling QtCreator because the qbscore library was
not found.
I then copied the compiled plugin into my precompiled Qt-5.2.1
directory and I was able to create a D project and edit a D file.
Unfortunately I wasn't able to
On Fri, 2014-07-04 at 07:46 +0100, Iain Buclaw via Digitalmars-d wrote:
[…]
> Powered by Martian Technology
@SarcasticRover is telling us "Do not come to Mars." Perhaps its
commentary need censoring ;-)
--
Russel.
=
Dr
On Friday, 4 July 2014 at 01:26:37 UTC, Walter Bright wrote:
The issues you presented are subjective and a matter of
opinion. Regardless of the state of D, I'm not the type who
wilts at an issue or two - I work around it. And so does
everyone else who does production work.
If you sit around
61 matches
Mail list logo
