In order:
1. A debugger (that works properly)
2. Go-to definition (that always works)
3. Auto-complete (that always works)
4. Import management (missing/duplicate/unused imports)
5. Typical suite of modern refactoring tools
On 27 January 2014 18:11, Manu wrote:
> In order:
>
> 1. A debugger (that works properly)
> 2. Go-to definition (that always works)
> 3. Auto-complete (that always works)
> 4. Import management (missing/duplicate/unused imports)
> 5. Typical suite of modern refactoring tools
>
I might add, the f
+1. Some of my unittests can only be run at runtime: like
testing file
I/O. Obviously, other unittests can also be run at
compile-time, so
it's useful to have both.
Tests that do I/O aren't unit tests. They're more likely
integration tests.
Atila
I share the opinion others have expressed here that running unit
tests should be the responsability of the build system.
Atila
On Saturday, 25 January 2014 at 22:55:33 UTC, Andrei Alexandrescu
wrote:
There's this simple realization that unittests could (should?)
be considered an intrinsic par
On Monday, 27 January 2014 at 08:12:14 UTC, Manu wrote:
In order:
1. A debugger (that works properly)
2. Go-to definition (that always works)
3. Auto-complete (that always works)
4. Import management (missing/duplicate/unused imports)
5. Typical suite of modern refactoring tools
Holly crap, I
. Static analysis
. Automated refactoring plugins for different editors
. Go to definition plugins for different editors
. Unused import warnings
. Some way of figuring out which import a function is from
Right now I'm glad that flycheck highlights compilation errors
for me in emacs, but unfortu
Thanks for responses. I considered to use scrypt for now, because
as described is's harder to hack it with brute force using GPU,
ASIC, FPGA than bcrypt. But it has some limitations too. I've
tried to tweak it to use more memory and less computation time
but failed. Another question for me is h
On Monday, 27 January 2014 at 08:24:07 UTC, Manu wrote:
On 27 January 2014 18:11, Manu wrote:
In order:
1. A debugger (that works properly)
2. Go-to definition (that always works)
3. Auto-complete (that always works)
4. Import management (missing/duplicate/unused imports)
5. Typical suite of
On Monday, 27 January 2014 at 09:08:04 UTC, Uranuz wrote:
Thanks for responses. I considered to use scrypt for now,
because as described is's harder to hack it with brute force
using GPU, ASIC, FPGA than bcrypt. But it has some limitations
too. I've tried to tweak it to use more memory and less
On Monday, 27 January 2014 at 07:16:26 UTC, Knud Soerensen wrote:
I miss check_expect from racket.
It is used for unit testing
check_expect(expression, result)
Will test if expression equals result
if it is not it print "Got expression but expected result" with
file and
line information.
In
On Monday, 27 January 2014 at 09:29:44 UTC, Rikki Cattermole
wrote:
On Monday, 27 January 2014 at 08:24:07 UTC, Manu wrote:
On 27 January 2014 18:11, Manu wrote:
In order:
1. A debugger (that works properly)
2. Go-to definition (that always works)
3. Auto-complete (that always works)
4. Impo
I can understand why you think about how I work, the way you do.
Its like the difference between an introvert and an extravert.
Its just so different way of working and thinking. Its
unbelievable.
I have honestly never meet somebody who works even similar to me.
On Sun, 2014-01-26 at 23:30 +, ed wrote:
[…]
> A quality GUI api with a decent GUI builder, something like the
> tools that come with Qt or that Window Builder for Java.
>
> I find GTKD bindings are great but the GTK api itself, IMO, is
> less intuitive than Qt and GTK+Glade is a lot more wo
On 27/01/2014 4:15 AM, Andrei Alexandrescu wrote:
On 1/26/14 8:08 PM, Jesse Phillips wrote:
On Monday, 27 January 2014 at 03:58:54 UTC, Andrei Alexandrescu wrote:
Yeppers. One other thought I had was to define a special flag e.g.
--4c5ad7908c2aa1b3de32ea25968cdf49 that says "just run unittests"
On 27 January 2014 19:29, Rikki Cattermole wrote:
> On Monday, 27 January 2014 at 08:24:07 UTC, Manu wrote:
>
>> On 27 January 2014 18:11, Manu wrote:
>>
>> In order:
>>>
>>> 1. A debugger (that works properly)
>>> 2. Go-to definition (that always works)
>>> 3. Auto-complete (that always works)
On 1/27/14, 1:04 AM, Andrei Alexandrescu wrote:
On 1/26/14 5:36 PM, Ary Borenszweig wrote:
On 1/25/14, 7:55 PM, Andrei Alexandrescu wrote:
There's this simple realization that unittests could (should?) be
considered an intrinsic part of the build process. In order for an
executable to be worth
On 2014-01-26 16:18, Frank Bauer wrote:
As you heard Andrei, too many *language features*, NOT *user code* rely
on objects staying around till the GC collects them. It's not a matter
of malloc/free everything in your user code. D as a language would not
work with this little gcstub.
Sure it wou
On 2014-01-27 09:11, Manu wrote:
In order:
1. A debugger (that works properly)
2. Go-to definition (that always works)
3. Auto-complete (that always works)
How well do these work for you in Visual Studio for C++? I'm finding
cases in Xcode where it doesn't always work, especially in DMD.
4
On Monday, 27 January 2014 at 11:10:04 UTC, Alix Pexton wrote:
On 27/01/2014 4:15 AM, Andrei Alexandrescu wrote:
On 1/26/14 8:08 PM, Jesse Phillips wrote:
On Monday, 27 January 2014 at 03:58:54 UTC, Andrei
Alexandrescu wrote:
Yeppers. One other thought I had was to define a special
flag e.g.
-
The URL http://dlang.org links to a page that just says "It
works!"
So laconic a statement for such a wonderful language! ;-)
Nicolas
On Monday, 27 January 2014 at 08:12:14 UTC, Manu wrote:
In order:
1. A debugger (that works properly)
2. Go-to definition (that always works)
3. Auto-complete (that always works)
4. Import management (missing/duplicate/unused imports)
5. Typical suite of modern refactoring tools
+1 for items 1
Am 27.01.2014 13:34, schrieb Nicolas Sicard:
The URL http://dlang.org links to a page that just says "It
works!"
So laconic a statement for such a wonderful language! ;-)
Nicolas
Looks fine from here.
On Monday, 27 January 2014 at 12:40:12 UTC, Sönke Ludwig wrote:
Am 27.01.2014 13:34, schrieb Nicolas Sicard:
The URL http://dlang.org links to a page that just says "It
works!"
So laconic a statement for such a wonderful language! ;-)
Nicolas
Looks fine from here.
From my home accout I have
On Monday, 27 January 2014 at 12:40:12 UTC, Sönke Ludwig wrote:
Am 27.01.2014 13:34, schrieb Nicolas Sicard:
The URL http://dlang.org links to a page that just says "It
works!"
So laconic a statement for such a wonderful language! ;-)
Nicolas
Looks fine from here.
Strange. I'll try again la
I need a rather simple but efficient 2D (but 3D would be even
better) plotting library for DSP visualization.
PLplot has D language bindings, however a search for PLplot on
this site pages returns only three old links.
Does anyone using PLplot can tell if it's worth using it or is
there any alte
On Monday, 27 January 2014 at 12:46:43 UTC, terchestor wrote:
I need a rather simple but efficient 2D (but 3D would be even
better) plotting library for DSP visualization.
PLplot has D language bindings, however a search for PLplot on
this site pages returns only three old links.
Does anyone usi
It's not dlang.org, it's dlang.org/index.html. I filed a
bugreport on this.
On 2014-01-25 22:55, Andrei Alexandrescu wrote:
[Good stuff]
What do you think? Logistically it shouldn't be too hard to arrange
things to cater to this approach.
As evinced by Bugzilla 5091[0], I always run unit tests separately from
the rest of the program, and so fully support this motion.
On 27 January 2014 22:14, Jacob Carlborg wrote:
> On 2014-01-27 09:11, Manu wrote:
>
>> In order:
>>
>> 1. A debugger (that works properly)
>> 2. Go-to definition (that always works)
>> 3. Auto-complete (that always works)
>>
>
> How well do these work for you in Visual Studio for C++? I'm findin
Pretty much only thing I really miss compared to C++ is full
valgrind support (including callgrind and helgrind).
There are a lot of things in tooling that could have been
improved, but those are not a deal breakers are my typical
development env is very minimalistic and does not rely on
anyt
El 27/01/14 13:54, John Colvin ha escrit:
> On Monday, 27 January 2014 at 12:46:43 UTC, terchestor wrote:
>> I need a rather simple but efficient 2D (but 3D would be even better)
>> plotting library for DSP visualization.
>> PLplot has D language bindings, however a search for PLplot on this site
On Monday, 27 January 2014 at 12:18:55 UTC, Idan Arye wrote:
How about exposing the sybmol of the function that runs the
unittest, and having a "dunittest" tool for running the tests
stored inside a regular executable? (I think it's possible?)
It is already possible via library solution.
On Saturday, 25 January 2014 at 13:43:25 UTC, Timon Gehr wrote:
Why not?
struct S{
auto opCmp(S r){ return float.nan; }
}
void main(){
S s;
assert(s!<>=s);
}
Yes, but only for floatingpoint types - you cannot overload the
!<>= operator for integral types and it will be deprecated
Question aimed at Daniel.
I noticed this change in the frontend merge:
---
@@ -4539,6 +4736,11 @@ TypeAArray::TypeAArray(Type *t, Type
*index)
this->sc = NULL;
}
+TypeAArray *TypeAArray::create(Type *t, Type *index)
+{
+return new TypeAArray(t, index);
+}
+
const char *TypeAArray::
On 01/27/2014 02:46 PM, Dominikus Dittes Scherkl wrote:
On Saturday, 25 January 2014 at 13:43:25 UTC, Timon Gehr wrote:
On 01/25/2014 01:57 PM, Dominikus Dittes Scherkl wrote:
And then comparison cannot be implemented fully correct with the current
operator overloding system of D.
Why not?
st
On Monday, 27 January 2014 at 08:12:14 UTC, Manu wrote:
In order:
1. A debugger (that works properly)
2. Go-to definition (that always works)
3. Auto-complete (that always works)
4. Import management (missing/duplicate/unused imports)
5. Typical suite of modern refactoring tools
It amazed me t
On 27 January 2014 15:00, Daniel Murphy wrote:
> "Iain Buclaw" wrote in message news:tahhleknrghaegcdv...@forum.dlang.org...
>
>> Question aimed at Daniel.
>
>
>> Assuming this needs to be done for all new'ing of classes across C++ -> D,
>> it looks like you've only done half a job? Surely you s
dub doesn't address my needs at all, but I've put crap loads of
time/energy
into the D extension for premake, which works well (
https://bitbucket.org/premakeext), although for some reason has
never
really gotten any attention from the D community :(
Never heard of the extension until now.
On Monday, 27 January 2014 at 11:32:04 UTC, Manu wrote:
[:snip:]
dub doesn't address my needs at all, but I've put crap loads of
time/energy
into the D extension for premake, which works well (
https://bitbucket.org/premakeext), although for some reason has
never
really gotten any attention fr
On Monday, 27 January 2014 at 14:27:42 UTC, Regan Heath wrote:
On Sat, 25 Jan 2014 10:15:28 -, Peter Alexander
wrote:
Special cases are pure evil. There's nothing special about
strings in this case.
This is a tangent to my suggestion.
I am arguing for domain specific language (aliases) w
On 1/26/14 10:08 PM, H. S. Teoh wrote:
On Sun, Jan 26, 2014 at 08:15:23PM -0800, Andrei Alexandrescu wrote:
On 1/26/14 8:08 PM, Jesse Phillips wrote:
On Monday, 27 January 2014 at 03:58:54 UTC, Andrei Alexandrescu wrote:
Yeppers. One other thought I had was to define a special flag e.g.
--4c5a
On 1/26/14 11:16 PM, Knud Soerensen wrote:
I miss check_expect from racket.
It is used for unit testing
check_expect(expression, result)
Will test if expression equals result
if it is not it print "Got expression but expected result" with file and
line information.
In D making unit tests is mo
I'm sure this was discussed at great length sometime, but
yesterday (and the day before) I had one of those days where I
turned on warnings , and told the compiler not to ignore
deprecated things.
Most of the warnings were probably due to keyboard repeats where
I had held a key down fractiona
"Iain Buclaw" wrote in message
news:mailman.99.1390837599.13884.digitalmar...@puremagic.com...
OK. Have you tested calling C++ destructors from D?
No, and I don't think they even mangle correctly.
This I ask in sincerity as there is a file with functions re-written
from the frontend to work
On Sat, 25 Jan 2014 10:15:28 -, Peter Alexander
wrote:
Special cases are pure evil. There's nothing special about strings in
this case.
This is a tangent to my suggestion.
I am arguing for domain specific language (aliases) where sensible, not
domain specific functions. If canFind ca
On 1/27/14 3:39 AM, Ary Borenszweig wrote:
On 1/27/14, 1:04 AM, Andrei Alexandrescu wrote:
On 1/26/14 5:36 PM, Ary Borenszweig wrote:
On 1/25/14, 7:55 PM, Andrei Alexandrescu wrote:
There's this simple realization that unittests could (should?) be
considered an intrinsic part of the build proc
On 1/27/14 3:10 AM, Alix Pexton wrote:
On 27/01/2014 4:15 AM, Andrei Alexandrescu wrote:
On 1/26/14 8:08 PM, Jesse Phillips wrote:
On Monday, 27 January 2014 at 03:58:54 UTC, Andrei Alexandrescu wrote:
Yeppers. One other thought I had was to define a special flag e.g.
--4c5ad7908c2aa1b3de32ea2
"Iain Buclaw" wrote in message news:tahhleknrghaegcdv...@forum.dlang.org...
Question aimed at Daniel.
Assuming this needs to be done for all new'ing of classes across C++ -> D,
it looks like you've only done half a job? Surely you should define a
::create for all Type's on the chance that
On 1/27/14 4:34 AM, Nicolas Sicard wrote:
The URL http://dlang.org links to a page that just says "It
works!"
So laconic a statement for such a wonderful language! ;-)
Nicolas
Sure you meant http://issues.dlang.org/
cc Brad Roberts
Andrei
On 1/27/14 6:27 AM, Regan Heath wrote:
On Sat, 25 Jan 2014 10:15:28 -, Peter Alexander
wrote:
Special cases are pure evil. There's nothing special about strings in
this case.
This is a tangent to my suggestion.
I am arguing for domain specific language (aliases) where sensible, not
domai
On 27 January 2014 16:04, Daniel Murphy wrote:
> "Iain Buclaw" wrote in message
> news:mailman.99.1390837599.13884.digitalmar...@puremagic.com...
>
>> OK. Have you tested calling C++ destructors from D?
>
>
> No, and I don't think they even mangle correctly.
>
>
>> This I ask in sincerity as the
Am 27.01.2014 09:23, schrieb Manu:
I made an interesting observation recently... D has kind of ruined my
career ;)
Before I started using D a lot, I found C/C++ quite okay as a language.
But after extended time using D, I find C/C++ borderline intolerable,
and don't enjoy writing it at all.
But t
That can be (and is) solved by D unit testing libraries.
Atila
On Monday, 27 January 2014 at 07:16:26 UTC, Knud Soerensen wrote:
I miss check_expect from racket.
It is used for unit testing
check_expect(expression, result)
Will test if expression equals result
if it is not it print "Got expre
On 1/27/14 6:13 AM, Timon Gehr wrote:
float opCmp(sint r){
if(isNan()||r.isNan()) return float.nan;
return valuer.value?1:0;
}
Quite a nice trick.
Andrei
On Monday, 27 January 2014 at 14:13:36 UTC, Timon Gehr wrote:
So? It was the most convenient way to illustrate that I have
defined a not fully ordered type using opCmp.
Was not my idea to deprecate them :-/
And you cannot opverload opCmp in a way that the new defined
integer NaN
will not com
"Iain Buclaw" wrote in message
news:mailman.100.1390839683.13884.digitalmar...@puremagic.com...
I tried that once before, only to be asked "Why are you doing this?" :o)
I still think 'verbose' is a good idea (that switch has zero coverage in the
test suite btw). But yeah, one thing at a time
On Monday, 27 January 2014 at 16:11:56 UTC, Andrei Alexandrescu
wrote:
Sure you meant http://issues.dlang.org/
That one is even more desriptive :)
Steve Teale:
I'm sure this was discussed at great length sometime, but
yesterday (and the day before) I had one of those days where I
turned on warnings , and told the compiler not to ignore
deprecated things.
A better compiler design is to have warning activated on default
and to be disabl
On 1/27/14 9:43 AM, Stanislav Blinov wrote:
On Monday, 27 January 2014 at 16:11:56 UTC, Andrei Alexandrescu wrote:
Sure you meant http://issues.dlang.org/
That one is even more desriptive :)
Issues.dlang.org isn't expected to work yet. I haven't done the work to move d.puremagic.com/issues
On 27 January 2014 16:50, Daniel Murphy wrote:
> "Iain Buclaw" wrote in message
> news:mailman.100.1390839683.13884.digitalmar...@puremagic.com...
>
>> I tried that once before, only to be asked "Why are you doing this?" :o)
>
>
> I still think 'verbose' is a good idea (that switch has zero cover
On Monday, 27 January 2014 at 16:06:46 UTC, Steve Teale wrote:
But as I plodded through my code base, I came across not a
single situation where the declaration of a virtual function in
some derived class was an error.
Based on my C++ memories it is quite common issue when working in
a teams
Based on my C++ memories it is quite common issue when working
in a teams because "Big Picture" is lacking. When you are main
sole contributor, keeping overall class layout in mind does not
seem to be any demanding.
That is of course true. The worst case then being that other
users add func
On Monday, 27 January 2014 at 17:57:02 UTC, Timon Gehr wrote:
On 01/26/2014 09:29 PM, Oten wrote:
Which tools do you miss in the D language? ...
A fully working compiler for the most recent language version.
Indeed, and robust documentation for it too.
On 01/26/2014 09:29 PM, Oten wrote:
Which tools do you miss in the D language? ...
A fully working compiler for the most recent language version.
On Monday, 27 January 2014 at 04:07:04 UTC, Andrei Alexandrescu
wrote:
On 1/26/14 3:22 AM, Pierre Talbot wrote:
Hi,
I was wondering why CTFE is context sensitive, why don't we
check
every expressions and run the CTFE if it applies?
Compilation would get awfully slow (and sometimes won't
te
On Sunday, 26 January 2014 at 19:56:59 UTC, Andrej Mitrovic wrote:
On 1/21/14, "@puremagic.com <"\"Théo".Bueno">
wrote:
Manjaro is great but keep in mind that you will not have access
to ArchLinux official repositories.
Speaking of Manjaro, does anyone know how to disable the
auto-update
feat
On Monday, 27 January 2014 at 17:55:35 UTC, Brad Roberts wrote:
On 1/27/14 9:43 AM, Stanislav Blinov wrote:
On Monday, 27 January 2014 at 16:11:56 UTC, Andrei
Alexandrescu wrote:
Sure you meant http://issues.dlang.org/
That one is even more desriptive :)
Issues.dlang.org isn't expected to
On Monday, 27 January 2014 at 18:35:24 UTC, Chris wrote:
On Sunday, 26 January 2014 at 19:56:59 UTC, Andrej Mitrovic
wrote:
On 1/21/14, "@puremagic.com <"\"Théo".Bueno">
wrote:
Manjaro is great but keep in mind that you will not have
access
to ArchLinux official repositories.
Speaking of Man
On Monday, 27 January 2014 at 08:27:57 UTC, Atila Neves wrote:
Right now I'm glad that flycheck highlights compilation errors
for me in emacs, but unfortunately there is no way currently to
pass it -I flags for different projects so any non-Phobos
non-currentdir imports fail.
Here's what I
On Monday, 27 January 2014 at 19:43:09 UTC, Chris wrote:
On Monday, 27 January 2014 at 18:35:24 UTC, Chris wrote:
On Sunday, 26 January 2014 at 19:56:59 UTC, Andrej Mitrovic
wrote:
On 1/21/14, "@puremagic.com <"\"Théo".Bueno">
wrote:
Manjaro is great but keep in mind that you will not have
acc
On Monday, 27 January 2014 at 18:30:43 UTC, Pierre Talbot wrote:
On Monday, 27 January 2014 at 04:07:04 UTC, Andrei Alexandrescu
wrote:
On 1/26/14 3:22 AM, Pierre Talbot wrote:
Hi,
I was wondering why CTFE is context sensitive, why don't we
check
every expressions and run the CTFE if it appl
On Monday, 27 January 2014 at 18:30:43 UTC, Pierre Talbot wrote:
On Monday, 27 January 2014 at 04:07:04 UTC, Andrei Alexandrescu
wrote:
On 1/26/14 3:22 AM, Pierre Talbot wrote:
Hi,
I was wondering why CTFE is context sensitive, why don't we
check
every expressions and run the CTFE if it appl
On Monday, 27 January 2014 at 21:12:30 UTC, deadalnix wrote:
lolwut ? How do you make the difference between a program that
won't terminate ever and one that will terminate eventually
(say, in several years) ?
1. The halting problem does not apply to finite resources. The
proof is trivial: ju
On Monday, 27 January 2014 at 20:42:57 UTC, Chris wrote:
Just found this. Interesting. Is the guy exaggerating or not?
http://aboutthebsds.wordpress.com/2013/03/31/bsd-vs-linux/
Found this forum post talking about the article :
https://www.linuxdistrocommunity.com/forums/showthread.php?tid=15
On Monday, 27 January 2014 at 20:42:57 UTC, Chris wrote:
Just found this. Interesting. Is the guy exaggerating or not?
http://aboutthebsds.wordpress.com/2013/03/31/bsd-vs-linux/
Stopped reading after GPL vs BSD license bullshit.
On 2014-01-27 21:37, "Ola Fosheim Grøstad"
"@puremagic.com wrote:
On Monday, 27 January 2014 at 21:12:30 UTC, deadalnix wrote:
lolwut ? How do you make the difference between a program that won't
terminate ever and one that will terminate eventually (say, in several
years) ?
1. The halting pro
On Linux, Mono-D seems to be pretty decent if you can actually
figure out how to install the thing.
Personally, I go with Geany+KDbg.
Geany is lightweight, supports D syntax, provides tabs, file
browsing, projects, built-in command promp, folder search, and
regex search and replace. If you wa
On Monday, 27 January 2014 at 21:37:58 UTC, Ola Fosheim Grøstad
wrote:
On Monday, 27 January 2014 at 21:12:30 UTC, deadalnix wrote:
lolwut ? How do you make the difference between a program that
won't terminate ever and one that will terminate eventually
(say, in several years) ?
1. The halti
On Fri, Jan 24, 2014 at 12:45 AM, Jesse Phillips <
jesse.k.phillip...@gmail.com> wrote:
> [...]
> You should probably file a bug. I think this change should be valid (it
> sounds like it wouldn't work, but didn't test)
>
There it is: https://d.puremagic.com/issues/show_bug.cgi?id=12014
LMB
On 2014-01-27 23:18, Tofu Ninja wrote:
On Monday, 27 January 2014 at 21:37:58 UTC, Ola Fosheim Grøstad wrote:
On Monday, 27 January 2014 at 21:12:30 UTC, deadalnix wrote:
lolwut ? How do you make the difference between a program that won't
terminate ever and one that will terminate eventually (
On 28 January 2014 01:47, Atila Neves wrote:
>
> dub doesn't address my needs at all, but I've put crap loads of
>> time/energy
>> into the D extension for premake, which works well (
>> https://bitbucket.org/premakeext), although for some reason has never
>> really gotten any attention from the
On 28 January 2014 11:16, Manu wrote:
> On 28 January 2014 01:47, Atila Neves wrote:
>
>>
>> dub doesn't address my needs at all, but I've put crap loads of
>>> time/energy
>>> into the D extension for premake, which works well (
>>> https://bitbucket.org/premakeext), although for some reason h
On Monday, 27 January 2014 at 12:34:30 UTC, Nicolas Sicard wrote:
The URL http://dlang.org links to a page that just says "It
works!"
So laconic a statement for such a wonderful language! ;-)
Nicolas
There certainly were some issues. Oddly mine had very strange
behavior. Instead of a webpage
"Iain Buclaw" wrote in message
news:mailman.103.1390845530.13884.digitalmar...@puremagic.com...
I have toyed around with the thought of moving backend specific
members into a Compiler struct which may vary across gdc, dmd, ldc...
I feel like Global should just be for frontend and semantic co
On 1/27/14 1:37 PM, "Ola Fosheim Grøstad"
" wrote:
On Monday, 27 January 2014 at 21:12:30 UTC, deadalnix wrote:
lolwut ? How do you make the difference between a program that won't
terminate ever and one that will terminate eventually (say, in several
years) ?
1. The halting problem does not a
Don't forget - Friday night is the deadline for both DConf submissions
and early registrations.
http://dconf.org
It's safe to say we have a quorum already. Also, the proposals we got
are solid. However, we are having fewer submissions, which is a bit of a
letdown.
Keep in mind: DConf is lit
On Monday, 27 January 2014 at 13:12:56 UTC, Manu wrote:
D doesn't have a preprocessor or a horrible network of text
include, it
should easily be able to match the C# experiences in general.
No, it's much, much harder because of templates and string mixins.
The only way to get a solid auto-com
On 28 January 2014 13:43, Jakob Ovrum wrote:
> On Monday, 27 January 2014 at 13:12:56 UTC, Manu wrote:
>
>> D doesn't have a preprocessor or a horrible network of text include, it
>> should easily be able to match the C# experiences in general.
>>
>
> No, it's much, much harder because of templat
On Tuesday, 28 January 2014 at 03:43:11 UTC, Jakob Ovrum wrote:
On Monday, 27 January 2014 at 13:12:56 UTC, Manu wrote:
D doesn't have a preprocessor or a horrible network of text
include, it
should easily be able to match the C# experiences in general.
No, it's much, much harder because of t
Support of MSVC COFF is really needed for me.
And x64 codegen without any dependencies like msvc's link.exe
linker.
90 matches
Mail list logo
