so wrote:
You cannot force inlining in C(++) either. The inline keyword is only
a suggestion.
I'm not understanding your last comment that a .lib would be required.
That's not correct, as since you're supplying the full source anyway
(needed for inlining), just compile in that source from
Jonathan M Davis Wrote:
On Thursday 10 February 2011 22:35:34 Walter Bright wrote:
Stewart Gordon wrote:
On 09/02/2011 12:14, spir wrote:
Hello,
Walter states that inline annotations are useless, since programmers
cannot generally know
which function /should/ be inlined
Jonathan M Davis wrote:
Regardless, I would _hope_ that the compiler would be smart enough to make
intelligent choices about inlining. That's probably one of those areas that can
always be improved however.
I agree completely. All compilers could use better register allocation
algorithms,
so wrote:
While in isolation that's a good idea, how far should it be taken?
Should the compiler emit information on which variables wound up in
which registers, and why? What about other of the myriad of compiler
optimizations?
Isn't Inlining by far the most important (most practical)
On 2011-02-11 04:15, Nick Sabalausky wrote:
Andrej Mitrovicandrej.mitrov...@gmail.com wrote in message
news:mailman.1476.1297391467.4748.digitalmar...@puremagic.com...
What the hell does to! have to do with anything. Disregard my last
post, it's obviously 3 AM and I'm talking gibberish.
I
On 2011-02-10 23:05, Andrei Alexandrescu wrote:
On 2/10/11 9:47 AM, spir wrote:
Even then, noone forces D2 to blindly reproduce stupid naming from
APL/C++, I guess. Or what?
I don't find the name iota stupid.
Andrei
Of course you don't think it's stupid, you named it. It starts to look
On 2011-02-11 08:39, Jim wrote:
Jacob Carlborg Wrote:
On 2011-02-10 20:15, Walter Bright wrote:
Nick Sabalausky wrote:
bearophilebearophileh...@lycos.com wrote in message
news:iivb5n$na3$1...@digitalmars.com...
auto x;
if (localtime().hours= 8) {
x = awake!
} else {
x = asleep, go away.
}
Jim Wrote:
Jacob Carlborg Wrote:
On 2011-02-10 20:15, Walter Bright wrote:
Nick Sabalausky wrote:
bearophile bearophileh...@lycos.com wrote in message
news:iivb5n$na3$1...@digitalmars.com...
auto x;
if (localtime().hours = 8) {
x = awake!
} else {
x = asleep, go away.
On 2/11/2011 12:37 AM, Walter Bright wrote:
so wrote:
While in isolation that's a good idea, how far should it be taken? Should
the compiler emit information on which
variables wound up in which registers, and why? What about other of the
myriad of compiler optimizations?
Isn't Inlining
No, not even close. The first step is figure out where your program is
slow, and then why it is slow. For example, if it is slow because foo()
is being called 1,000,000 times, you'll get a one thousand times speedup
if you can tweak your algorithms so that it is only called 1,000 times.
I
Wrappers and frequent matrix, vector operations are -a- very serious
examples that inlining is must. Now, it doesn't matter how easy or hard,
-have- +how+ could we get around this?
This is a great +excuse+ for an annotation.
duh... how hard to synchronize brain, hands and eyes...
On 02/11/2011 07:13 AM, Jonathan M Davis wrote:
We _must_ have it there, so anyone overriding those functions _must_
use it for those functions. They could create non-const versions in
addition to
the const ones,
It is the whole point, they can't.
Hmm. You're right (I just tried
On 02/11/2011 09:33 AM, Jim wrote:
Regardless, I would _hope_ that the compiler would be smart enough to make
intelligent choices about inlining. That's probably one of those areas that
can
always be improved however.
I also think that this decision should be left to the compiler.
The
Walter:
While in isolation that's a good idea, how far should it be taken? Should the
compiler emit information on which variables wound up in which registers, and
why? What about other of the myriad of compiler optimizations?
Inlining is an important optimization, so give this information
On 02/11/2011 08:39 AM, Jim wrote:
Jacob Carlborg Wrote:
On 2011-02-10 20:15, Walter Bright wrote:
Nick Sabalausky wrote:
bearophilebearophileh...@lycos.com wrote in message
news:iivb5n$na3$1...@digitalmars.com...
auto x;
if (localtime().hours= 8) {
x = awake!
} else {
x = asleep, go away.
On 02/11/2011 03:06 AM, Jonathan M Davis wrote:
I feel pretty much the same way. iota seems like a horrible name as far as
figuring out what the function does from its name goes. I don't know what a good
name would be though (genSequence?)
why not interval? (not obvious enough ;-)
denis
--
On 02/11/2011 02:38 AM, Nick Sabalausky wrote:
Max Samukhamaxsamu...@spambox.com wrote in message
news:ij10n7$25p0$1...@digitalmars.com...
On 02/10/2011 05:18 PM, Andrei Alexandrescu wrote:
On 2/10/11 12:30 AM, Olivier Pisano wrote:
Le 09/02/2011 21:08, Ary Manzana a écrit :
On 2/9/11 3:54
On Friday 11 February 2011 02:43:11 spir wrote:
On 02/11/2011 07:13 AM, Jonathan M Davis wrote:
We _must_ have it there, so anyone overriding those functions _must_
use it for those functions. They could create non-const versions
in addition to
the const ones,
It
But I'm sure this sort of thing is also highly variable based on type of
applications, code style, language, etc.
Indeed it is, for example you won't hear much complaints from game
developers because they rely on GPU for most of the computations these
days,
but there are other areas where
On 02/11/2011 07:32 AM, Walter Bright wrote:
spir wrote:
Thus, at best, we would need to know a bit about criteria used by the
compiler for deciding whether to inline or not; provided a doc explaining
this is at all readable by people who do not have the compiler-writer gene.
Aside that, let us
On 02/11/2011 07:53 AM, so wrote:
While in isolation that's a good idea, how far should it be taken? Should the
compiler emit information on which variables wound up in which registers, and
why? What about other of the myriad of compiler optimizations?
Isn't Inlining by far the most important
spir:
People possibly interested in the question of inlining (or more generally
factors of (in)efficiency) must start somehow, granted. But making it even
more
difficult than necessary, while we all know it is inherently a very complex
topic, does not bring much, don't you think?
In
On 09/02/2011 23:02, Ulrik Mikaelsson wrote:
2011/2/9 Bruno Medeirosbrunodomedeiros+spam@com.gmail:
It's unlikely you will see converted repositories with a lot of changing
blob data. DVCS, at the least in the way they work currently, simply kill
this workflow/organization-pattern.
I very much
Andrei Alexandrescu Wrote:
I don't find the name iota stupid.
Andrei
Of course _you_ don't. However practically all the users _do_ find it poorly
named, including other developers in the project..
This is the umpteenth time this comes up in the NG and incidentally this is the
only
On 09/02/2011 14:27, Michel Fortin wrote:
On 2011-02-09 07:49:31 -0500, Bruno Medeiros
brunodomedeiros+spam@com.gmail said:
On 04/02/2011 20:11, Michel Fortin wrote:
On 2011-02-04 11:12:12 -0500, Bruno Medeiros
brunodomedeiros+spam@com.gmail said:
Can Git really have an usable but
On Mon, 07 Feb 2011 10:37:46 -0500, Robert Jacques wrote:
On Mon, 07 Feb 2011 07:40:30 -0500, Steven Schveighoffer
schvei...@yahoo.com wrote:
On Fri, 04 Feb 2011 17:36:50 -0500, Tomek Sowiński j...@ask.me wrote:
Steven Schveighoffer napisał:
Here is how I would approach it (without doing
On 30/01/2011 08:03, Andrei Alexandrescu wrote:
I've had some style updates from David Gileadi rotting in a zip file in
my inbox for a good while. It took me the better part of today to
manually merge his stale files with the ones in the repository, which
have in the meantime undergone many
Bruno Medeiros Wrote:
On 09/02/2011 23:02, Ulrik Mikaelsson wrote:
2011/2/9 Bruno Medeirosbrunodomedeiros+spam@com.gmail:
It's unlikely you will see converted repositories with a lot of changing
blob data. DVCS, at the least in the way they work currently, simply kill
this
On 04/02/2011 21:07, Steven Schveighoffer wrote:
On Fri, 04 Feb 2011 15:44:46 -0500, Jeff Nowakowski j...@dilacero.org
wrote:
On 02/03/2011 10:07 PM, Walter Bright wrote:
The way to get a high performance string parser in D is to take
advantage of one of D's unique features - slices. Java,
spir Wrote:
On 02/11/2011 08:39 AM, Jim wrote:
Jacob Carlborg Wrote:
On 2011-02-10 20:15, Walter Bright wrote:
Nick Sabalausky wrote:
bearophilebearophileh...@lycos.com wrote in message
news:iivb5n$na3$1...@digitalmars.com...
auto x;
if (localtime().hours= 8) {
x = awake!
}
On 06/02/2011 21:30, Jacob Carlborg wrote:
On 2011-02-06 20:59, Walter Bright wrote:
Jacob Carlborg wrote:
On 2011-02-04 20:33, Walter Bright wrote:
so wrote:
It doesn't matter what signature you use for the function, compiler is
aware and will output an error when you do the opposite of the
spir Wrote:
On 02/11/2011 09:33 AM, Jim wrote:
Regardless, I would _hope_ that the compiler would be smart enough to make
intelligent choices about inlining. That's probably one of those areas
that can
always be improved however.
I also think that this decision should be left
On Fri, 11 Feb 2011 08:19:51 -0500, Bruno Medeiros
brunodomedeiros+spam@com.gmail wrote:
On 04/02/2011 21:07, Steven Schveighoffer wrote:
On Fri, 04 Feb 2011 15:44:46 -0500, Jeff Nowakowski j...@dilacero.org
wrote:
On 02/03/2011 10:07 PM, Walter Bright wrote:
The way to get a high
On 18/12/2010 12:46, Don wrote:
spir wrote:
On Sat, 18 Dec 2010 01:08:20 -0800
Jonathan M Davis jmdavisp...@gmx.com wrote:
Thank you for the explanation about strongly pure funcs calling weakly
pure ones --this fully makes sense.
I would like weakly pure to include output funcs, and exclude
Recently I tried std.regex, and must say Im very satisfied with new interface.
Just one small objection, I think captures range dont need match.hit at front.
But I can live with it :)
On 2/11/11 12:15 AM, Nick Sabalausky wrote:
Andrej Mitrovicandrej.mitrov...@gmail.com wrote in message
news:mailman.1476.1297391467.4748.digitalmar...@puremagic.com...
What the hell does to! have to do with anything. Disregard my last
post, it's obviously 3 AM and I'm talking gibberish.
I
On Fri, 11 Feb 2011 09:06:06 -0500, Ary Manzana a...@esperanto.org.ar
wrote:
On 2/11/11 12:15 AM, Nick Sabalausky wrote:
Andrej Mitrovicandrej.mitrov...@gmail.com wrote in message
news:mailman.1476.1297391467.4748.digitalmar...@puremagic.com...
What the hell does to! have to do with
On Fri, 11 Feb 2011 09:06:06 -0500, Ary Manzana a...@esperanto.org.ar
wrote:
On 2/11/11 12:15 AM, Nick Sabalausky wrote:
Andrej Mitrovicandrej.mitrov...@gmail.com wrote in message
news:mailman.1476.1297391467.4748.digitalmar...@puremagic.com...
What the hell does to! have to do with
On 11/02/2011 13:48, Steven Schveighoffer wrote:
On Fri, 11 Feb 2011 08:19:51 -0500, Bruno Medeiros
brunodomedeiros+spam@com.gmail wrote:
On 04/02/2011 21:07, Steven Schveighoffer wrote:
On Fri, 04 Feb 2011 15:44:46 -0500, Jeff Nowakowski j...@dilacero.org
wrote:
On 02/03/2011 10:07 PM,
Am 10.02.2011 12:40, schrieb spir:
Certainly, because it's /highly/ important for a community of programmers to
share the same culture. And names are the main support vehicle for this
culture.
Denis
(For this reason, I stoppped aliasing size_t and size_diff_t to Ordinal and
Cardinal
On 04/02/2011 16:14, Eric Poggel wrote:
On 2/3/2011 10:20 PM, Andrei Alexandrescu wrote:
At this point there is no turning back from ranges, unless we come about
with an even better idea (I discussed one with Walter but we're not
pursuing it yet).
Care to elaborate on the new idea? Or at
On 2011-02-11 09:29:03 -0500, Bruno Medeiros
brunodomedeiros+spam@com.gmail said:
On 11/02/2011 13:48, Steven Schveighoffer wrote:
I think D can do it without copying out of the buffer. You just have to
avoid using immutable strings.
-Steve
The data that you want to keep afterwards you
Am 09.02.2011 23:56, schrieb Ulrik Mikaelsson:
Maybe it's [JavaScript] the ASM of next decade.
Bringing the performance of the second last decades systems to hardware of the
next decade.
Hooray \o/
On 02/10/2011 10:08 PM, Nick Sabalausky wrote:
Regarding Java 1.3/1.4: They may very well have been closer to 1.2 than they
were to 1.5/1.6 (I wouldn't know), but IIRC 1.3 was when it finally started
to give people little bits of suger (ex: foreach).
1.5 was when Java got foreach, generics,
On 02/11/2011 03:05 PM, jovo wrote:
Recently I tried std.regex, and must say I’m very satisfied with new interface.
Just one small objection, I think captures range don’t need match.hit at front.
???
Denis
--
_
vita es estrany
spir.wikidot.com
Bruno Medeiros:
Hum, it might still be useful to have something like a compiler switch
that disables pure altogether, then people could use I/O and other
non-pure operations for debugging purposes. One could wrap such code
with a version statement:
void myPurefunc(Foo foo) pure {
On 02/11/2011 03:32 PM, Daniel Gibson wrote:
Am 10.02.2011 12:40, schrieb spir:
Certainly, because it's /highly/ important for a community of programmers to
share the same culture. And names are the main support vehicle for this
culture.
Denis
(For this reason, I stoppped aliasing size_t
Jim:
I rarely need to go that low-level.
Two times I have had D1 code that was too much slow compared to equivalent C
code. After profiling and some changes I have understood that the cause was an
important missing inline. With a list of the inlined functions (as done by
CommonLisp some
spir:
But for 99% uses of cardinals and ordinals uint is by far big enough.
Then in D2 for those use an int. Unsigned values are _very_ bug-prone in D2.
Bye,
bearophile
On 02/11/2011 07:08 PM, bearophile wrote:
Jim:
I rarely need to go that low-level.
Two times I have had D1 code that was too much slow compared to equivalent C
code. After profiling and some changes I have understood that the cause was an
important missing inline. With a list of the
On 2011-02-11 08:05:27 -0500, Bruno Medeiros
brunodomedeiros+spam@com.gmail said:
On 09/02/2011 14:27, Michel Fortin wrote:
On 2011-02-09 07:49:31 -0500, Bruno Medeiros
brunodomedeiros+spam@com.gmail said:
I was about to say Cool!, but then I checked the doc on that link
and it says:
A
On 2/10/11 5:29 PM, Sean Kelly wrote:
Andrei Alexandrescu Wrote:
I don't find the name iota stupid.
I never entirely understood the name choice. I suppose iota could be related to a
small step so iota(1,5) is a series of small steps from 1 to 5?
Pretty much, with the note that the
On 2/10/11 8:28 PM, Andrej Mitrovic wrote:
What the hell does to! have to do with anything. Disregard my last
post, it's obviously 3 AM and I'm talking gibberish.
In any case,
alias iota range;
Problem solved for me!
Aside from the fact that range has another meaning in D, the word does
not
Ok, bumping this up with the latest news from UniLink developers:
quote
Ok, we release it's as D extension in next release.
Best regards,
UniLink
/quote
That's just plain awesome ;)
--
Dmitry Olshansky
bearophile wrote:
While in isolation that's a good idea, how far should it be taken? Should the
compiler emit information on which variables wound up in which registers, and
why? What about other of the myriad of compiler optimizations?
Inlining is an important optimization, so give this
Jeff Nowakowski wrote:
1.5 was when Java got foreach, generics, and enum. I don't think there
were any syntactical language changes before that. Previous version
updates were mostly about libraries and frameworks.
Inner classes were added earlier.
Am 11.02.2011 19:56, schrieb Dmitry Olshansky:
Ok, bumping this up with the latest news from UniLink developers:
quote
Ok, we release it's as D extension in next release.
Best regards,
UniLink
/quote
That's just plain awesome ;)
Great :)
== Quote from bearophile (bearophileh...@lycos.com)'s article
To avoid troubles in generic code you need a little workaround:
if (__traits(isUnsigned, x) || x = 0) { ...
That's not good enough yet. The first part of the test needs to be done in a
static if.
Bye,
bearophile
You also need to
On 2/11/11, Andrei Alexandrescu seewebsiteforem...@erdani.org wrote:
On 2/10/11 8:28 PM, Andrej Mitrovic wrote:
What the hell does to! have to do with anything. Disregard my last
post, it's obviously 3 AM and I'm talking gibberish.
In any case,
alias iota range;
Problem solved for me!
Hello,
Just had a strange bug --in a test func!-- caused by this notation. This is due
in my case to the practice (common, I guess) of pretty printing int numbers
using %0nd or %0ns format, to get a nice alignment. Then, if one feeds back
results into D code, they are interpreted as octal...
bearophile Wrote:
The LLVM back-end of LDC is able to inline much more, but even here a list of
inlined/not inlined functions helps. D is almost a system language, so
sometimes you need to go lower level (or you just need a program that's not
too much slow).
If forced inlining is to be
bearophile Wrote:
Then in D2 for those use an int. Unsigned values are _very_ bug-prone in D2.
May I ask why?
On 02/11/2011 08:11 PM, Walter Bright wrote:
bearophile wrote:
While in isolation that's a good idea, how far should it be taken? Should
the compiler emit information on which variables wound up in which
registers, and why? What about other of the myriad of compiler optimizations?
Inlining is
spir Wrote:
Hello,
Just had a strange bug --in a test func!-- caused by this notation. This is
due
in my case to the practice (common, I guess) of pretty printing int numbers
using %0nd or %0ns format, to get a nice alignment. Then, if one feeds back
results into D code, they are
Jim Wrote:
bearophile Wrote:
The LLVM back-end of LDC is able to inline much more, but even here a list
of inlined/not inlined functions helps. D is almost a system language, so
sometimes you need to go lower level (or you just need a program that's not
too much slow).
If forced
Jim:
bearophile Wrote:
Then in D2 for those use an int. Unsigned values are _very_ bug-prone in D2.
May I ask why?
Because:
- D unsigned numbers are fixed-sized bitfields, they overflow. (Multi-precision
values are not built-in, they are currently slow if you need a 30 or 50 or 70
bit
We actually have a library replacement for octal literals:
http://dpldocs.info/octal
But until the C style syntax is disallowed, it doesn't change
anything. But, Walter is resistant to the change, last I knew.
spir:
like 0onnn, which is
consistent with common hex bin notations and cannot lead to
misinterpretation. Such a change would be, I guess, backward compatible; and
would not be misleading for C coders.
The 0nnn octal syntax is bug-prone, and not explicit, it's out of place in a
language
Andrei:
Aside from the fact that range has another meaning in D, the word does
not convey the notion that iota adds incremental steps to move from one
number to another. Iota does convey that notion.
I have accepted the iota name, it's short, easy to remember, it has one
historical usage
Jim:
If forced inlining is to be supported
spir was asking for a list of functions that the compiled has inlined, not for
a forced inlining functionality.
Bye,
bearophile
On 02/10/11 13:49, Andrej Mitrovic wrote:
On 2/10/11, Walter Bright newshou...@digitalmars.com wrote:
auto x = (localtime().hours = 8) ? awake! : asleep, go away.;
Aye, a one liner!
I hate seeing things like this:
if (funcall())
{
var = foo;
}
else
{
var = bar;
}
So much
Walter:
bearophile wrote:
While in isolation that's a good idea, how far should it be taken? Should
the
compiler emit information on which variables wound up in which registers,
and
why? What about other of the myriad of compiler optimizations?
Inlining is an important
Iain Buclaw:
You also need to watch out for code like this too:
if (T.min 0) { ...
As that could possibly trigger off unsigned 0 warnings too.
I was not talking about warnings. I was talking about changing the D language,
turning that into a _error_ if x is unsigned.
Bye,
bearophile
spir:
About inline, note that no-one asks for information on every potentially
inlinable func, blindly. But having a way to know that about /this/ func one
is
wondering about would be great: just append @inline to it, recompile, et
voilà !
you know :-) (provided you can interpret the
On 02/11/11 14:26, Jim wrote:
Jim Wrote:
bearophile Wrote:
The LLVM back-end of LDC is able to inline much more, but even here a list
of inlined/not inlined functions helps. D is almost a system language, so
sometimes you need to go lower level (or you just need a program that's not
too
spir denis.s...@gmail.com wrote in message
news:mailman.1504.1297453559.4748.digitalmar...@puremagic.com...
Hello,
Just had a strange bug --in a test func!-- caused by this notation. This
is due in my case to the practice (common, I guess) of pretty printing
int numbers using %0nd or %0ns
Steven Schveighoffer schvei...@yahoo.com wrote in message
news:op.vqqsdxcaeav7ka@steve-laptop...
According to the book The Design of Everyday Things the design of that
function name is wrong, it's not your fault and it's not because it was
3am. When many people make mistakes with regards to
On 02/11/2011 09:49 PM, bearophile wrote:
Jim:
If forced inlining is to be supported
spir was asking for a list of functions that the compiled has inlined, not for
a forced inlining functionality.
You are (nearly) right, Bearophile. More precisely, I rather wish @inline on a
given func
On 2/11/11, Christopher Nicholson-Sauls ibisbase...@gmail.com wrote:
Even better:
switch( funcall() ) {
case foo, bar, foobar, barfoo: {
// complex code
break;
}
case blue, green: {
// complex code
break;
}
default:
// do
bearophile bearophileh...@lycos.com wrote in message
news:ij473k$1tfn$1...@digitalmars.com...
Andrei:
Aside from the fact that range has another meaning in D, the word does
not convey the notion that iota adds incremental steps to move from one
number to another. Iota does convey that
On 02/11/2011 10:22 PM, Christopher Nicholson-Sauls wrote:
On 02/11/11 14:26, Jim wrote:
Jim Wrote:
bearophile Wrote:
The LLVM back-end of LDC is able to inline much more, but even here a list of
inlined/not inlined functions helps. D is almost a system language, so
sometimes you need to
On 02/11/2011 10:08 PM, bearophile wrote:
spir:
About inline, note that no-one asks for information on every potentially
inlinable func, blindly. But having a way to know that about /this/ func one is
wondering about would be great: just append @inline to it, recompile, et voilà!
you know :-)
On Fri, 11 Feb 2011 17:03:13 -0500, Nick Sabalausky a@a.a wrote:
Steven Schveighoffer schvei...@yahoo.com wrote in message
news:op.vqqsdxcaeav7ka@steve-laptop...
According to the book The Design of Everyday Things the design of
that
function name is wrong, it's not your fault and it's not
Nick Sabalausky:
I really should actually read that book.
Donald Norman is not a genius, he seems to lack both in engineering knowledge
and classic literary culture, but despite this he has the right mindset to
explore the world and he does look a lot at the world and its things, so he
ends
Steven Schveighoffer schvei...@yahoo.com wrote in message
news:op.vqrewtcfeav7ka@steve-laptop...
On Fri, 11 Feb 2011 17:03:13 -0500, Nick Sabalausky a@a.a wrote:
Steven Schveighoffer schvei...@yahoo.com wrote in message
news:op.vqqsdxcaeav7ka@steve-laptop...
According to the book The Design
foobar f...@bar.com wrote in message news:ij3cal$cee$1...@digitalmars.com...
Andrei Alexandrescu Wrote:
I don't find the name iota stupid.
Andrei
Of course _you_ don't. However practically all the users _do_ find it
poorly named, including other developers in the project..
This is the
Ary Manzana Wrote:
On 2/11/11 12:15 AM, Nick Sabalausky wrote:
Andrej Mitrovicandrej.mitrov...@gmail.com wrote in message
news:mailman.1476.1297391467.4748.digitalmar...@puremagic.com...
What the hell does to! have to do with anything. Disregard my last
post, it's obviously 3 AM and I'm
spir napisał:
Just had a strange bug --in a test func!-- caused by this notation. This is
due
in my case to the practice (common, I guess) of pretty printing int numbers
using %0nd or %0ns format, to get a nice alignment. Then, if one feeds back
results into D code, they are interpreted
Bruno Medeiros brunodomedeiros+spam@com.gmail wrote:
In this code sample if the optimization is applied on the second call to
func, it would cause different code with be executed: the else clause
instead of the then clause. Obviously this is not acceptable for an
optimization, even if such
Bruno Medeiros brunodomedeiros+spam@com.gmail wrote:
I think he means that any use of an @unimplemented class should give a
warning/error/other message.
I think you definitely get an error when trying to use a commented out
class/struct... :)
Absolutely. But such a class/struct would
spir wrote:
On 02/11/2011 08:11 PM, Walter Bright wrote:
bearophile wrote:
While in isolation that's a good idea, how far should it be taken?
Should
the compiler emit information on which variables wound up in which
registers, and why? What about other of the myriad of compiler
On 02/11/2011 10:54 PM, Nick Sabalausky wrote:
spirdenis.s...@gmail.com wrote in message
news:mailman.1504.1297453559.4748.digitalmar...@puremagic.com...
Hello,
Just had a strange bug --in a test func!-- caused by this notation. This
is due in my case to the practice (common, I guess) of
bearophile wrote:
There are two groups of register allocation algorithms. The very
fast ones, and the more precise ones. You even have perfect ones. Experience
has shown that the difference in runtime performance between the precise
algorithm and the perfect ones is often about 5% (this measured
Bruno Medeiros wrote:
but seriously, even if I am
connected to the Internet I cannot code with my laptop only, I need it
connected to a monitor, as well as a mouse, (and preferably a keyboard
as well).
I found I can't code on my laptop anymore; I am too used to and needful of a
large
On 2/11/11 2:46 AM, Jacob Carlborg wrote:
On 2011-02-10 23:05, Andrei Alexandrescu wrote:
On 2/10/11 9:47 AM, spir wrote:
Even then, noone forces D2 to blindly reproduce stupid naming from
APL/C++, I guess. Or what?
I don't find the name iota stupid.
Andrei
Of course you don't think it's
On 2/2/11, Andrei Alexandrescu seewebsiteforem...@erdani.org wrote:
Following ideas and advice from this newsgroup, I have a draft at
http://d-programming-language.org/cutting-edge/phobos/std_algorithm.html
Andrei
You know, we could use the same thing for the language reference. E.g.:
On 2/11/11 7:07 AM, foobar wrote:
Andrei Alexandrescu Wrote:
I don't find the name iota stupid.
Andrei
Of course _you_ don't. However practically all the users _do_ find it
poorly named, including other developers in the project.. This is the
umpteenth time this comes up in the NG and
Register allocation is far more important than inlining. Why not give
information about why a variable was not enregistered?
I am sorry Walter but your stance on this more politic than a practical
fact, it is not you, sounds like you secured a professorship!. :)
On 2/11/11 8:32 AM, Daniel Gibson wrote:
Am 10.02.2011 12:40, schrieb spir:
Certainly, because it's /highly/ important for a community of programmers to
share the same culture. And names are the main support vehicle for this
culture.
Denis
(For this reason, I stoppped aliasing size_t and
On 2/11/11 8:31 AM, Bruno Medeiros wrote:
On 04/02/2011 16:14, Eric Poggel wrote:
On 2/3/2011 10:20 PM, Andrei Alexandrescu wrote:
At this point there is no turning back from ranges, unless we come about
with an even better idea (I discussed one with Walter but we're not
pursuing it yet).
1 - 100 of 190 matches
Mail list logo
