On Fri, 24 May 2013 07:02:52 -0400
Andrei Alexandrescu seewebsiteforem...@erdani.org wrote:
It's there!
http://www.reddit.com/r/programming/comments/1eyq5z/dconf_2013_day_2_talk_1_gdc_by_iain_buclaw/
Andrei
Torrents: http://semitwist.com/download/misc/dconf2013/
On Tuesday, 21 May 2013 at 20:36:20 UTC, Walter Bright wrote:
Join the dmd beta mailing list to keep up with the betas. This
one is pretty much good to go, unless something disastrous
crops up.
http://ftp.digitalmars.com/dmd2beta.zip
Remaining regressions:
Wonderful talk, Iain. :-)
One question about the copyright assignment issue. How does this
operate in practice? Is it going to be that the D frontend will
simply go forward as copyright (c) FSF (which isn't a problem
DMD-wise as their assignment agreement immediately licenses the
code back
On 25 May 2013 14:52, Joseph Rushton Wakeling
joseph.wakel...@webdrake.net wrote:
Wonderful talk, Iain. :-)
One question about the copyright assignment issue. How does this operate in
practice? Is it going to be that the D frontend will simply go forward as
copyright (c) FSF (which isn't a
Hello,
We figured a workflow that allows us to make the source of dconf.org public.
We plan to adapt the design for next year's event, so if you have any
ideas feel free to take a look.
https://github.com/D-Programming-Language/dconf.org
Thanks,
Andrei
On 5/26/13, Andrei Alexandrescu seewebsiteforem...@erdani.org wrote:
We plan to adapt the design for next year's event
So I guess this makes it official that we're going to have a DConf
2014? Pretty cool.
Any ideas where it will be hosted, or where you'd want to host it?
On 5/25/13 7:30 PM, Andrej Mitrovic wrote:
On 5/26/13, Andrei Alexandrescuseewebsiteforem...@erdani.org wrote:
We plan to adapt the design for next year's event
So I guess this makes it official that we're going to have a DConf
2014? Pretty cool.
Barring unforeseen circumstances, yes.
On Friday, 24 May 2013 at 21:21:27 UTC, Dmitry Olshansky wrote:
You seem to think that not only UTF-8 is bad encoding but also
one unified encoding (code-space) is bad(?).
Yes, on the encoding, if it's a variable-length encoding like
UTF-8, no, on the code space. I was originally going to
On Friday, 24 May 2013 at 22:44:24 UTC, H. S. Teoh wrote:
I remember those bad ole days of gratuitously-incompatible
encodings. I
wish those days will never ever return again. You'd get a text
file in
some unknown encoding, and the only way to make any sense of it
was to
guess what encoding it
Am 25.05.2013 07:52, schrieb Manu:
On 25 May 2013 15:29, deadalnix deadal...@gmail.com
mailto:deadal...@gmail.com wrote:
On Saturday, 25 May 2013 at 05:18:12 UTC, Manu wrote:
On 25 May 2013 15:00, deadalnix deadal...@gmail.com
mailto:deadal...@gmail.com wrote:
On Saturday, 25 May 2013 at 05:52:23 UTC, Manu wrote:
But it would be deterministic, and if the allocations are few,
the cost
should be negligible.
You'll pay a tax on pointer write, not on allocations ! It won't
be negligible !
They're still non-deterministic though. And unless (even
Am 25.05.2013 03:29, schrieb Manu:
On 25 May 2013 04:20, Benjamin Thaut c...@benjamin-thaut.de
mailto:c...@benjamin-thaut.de wrote:
[...]
See, I have spend a decade on core tech/engine code meticulously
worrying about memory allocation. I don't think a GC is an outright no-go.
But we certainly
On Saturday, 25 May 2013 at 01:58:41 UTC, Walter Bright wrote:
One of the first, and best, decisions I made for D was it would
be Unicode front to back.
That is why I asked this question here. I think D is still one
of the few programming languages with such unicode support.
This is more a
I think you are a little confused about what unicode actually
is... Unicode has nothing to do with code pages and nobody uses
code pages any more except for compatibility with legacy
applications (with good reason!).
Unicode is:
1) A standardised numbering of a large number of characters
2) A
On Tuesday, 7 May 2013 at 20:17:43 UTC, QAston wrote:
No. A tutorial on memory consistency models would be too long
to insert here. I don't know of a good online resource, does
anyone?
Andrei
This was very helpful for me - focuses much more on the memory
model itself than the c++11 part.
On Saturday, 25 May 2013 at 07:48:05 UTC, Diggory wrote:
I think you are a little confused about what unicode actually
is... Unicode has nothing to do with code pages and nobody uses
code pages any more except for compatibility with legacy
applications (with good reason!).
Incorrect.
Unicode
What's the official status of shared libraries in dmd 2.063? Is it
already deemed stable or can there still be breaking changes for dmd
2.064?
I'm asking because I think we should change the default visibility of D
functions in shared libraries. We want to encourage platform
independent code so
On 5/25/2013 12:33 AM, Joakim wrote:
At what cost? Most programmers completely punt on unicode, because they just
don't want to deal with the complexity. Perhaps you can deal with it and don't
mind the performance loss, but I suspect you're in the minority.
I think you stand alone in your
On Saturday, 25 May 2013 at 07:33:15 UTC, Joakim wrote:
This is more a problem with the algorithms taking the easy way
than a problem with UTF-8. You can do all the string
algorithms, including regex, by working with the UTF-8
directly rather than converting to UTF-32. Then the algorithms
On Saturday, 25 May 2013 at 08:42:46 UTC, Walter Bright wrote:
I think you stand alone in your desire to return to code pages.
Nobody is talking about going back to code pages. I'm talking
about going to single-byte encodings, which do not imply the
problems that you had with code pages way
I just tried out Sublime Text 2 and found it to be quite similar
but somewhat better than TextMate 2. And there's an improved D
syntax highlighter for it at: https://github.com/alexrp/st2-d
All the keywords seem to be there, indentation works etc.
Sublime Text does from time to time annoy you
On Saturday, 25 May 2013 at 08:58:57 UTC, Vladimir Panteleev
wrote:
Another thing I noticed: sometimes when you think you really
need to operate on individual characters (and that your code
will not be correct unless you do that), the assumption will be
incorrect due to the existence of
As those of you who do write some non-toy projects in D know, from time
to time you projects become unbuildable because of Issue 9044 [1] an you
have to juggle with files and randomly copy/move functions from one
library to another to detrigger the issue creating mess marked Issue
9044
This is dumb. You are dumb. Go away.
On Saturday, 25 May 2013 at 09:40:36 UTC, Joakim wrote:
Can you post some specific cases where the benefits of a
constant-width encoding are obvious and, in your opinion, make
constant-width encodings more useful than all the benefits of
UTF-8?
Let's take one you listed above, slicing a
Hi,
In D, the : in a template parameter list only binds to 1
parameter.
There is no way to specialize upon the entire template parameter
list.
Therefore you can't do much with the pattern matching and it's
not powerful.
Not a reasonable situation for a language aiming to be only the
best.
On Saturday, 25 May 2013 at 10:07:29 UTC, Denis Shelomovskij
wrote:
obviously contradicts my personal very loyal definition (e.g. I
have noting against breaking changes if they are in good
direction).
I very much like this definition.
Am 25.05.2013 03:29, schrieb Manu:
Win64 works for me out of the box... ?
For me dmd produces type names like modulename.typename.subtypename
which will causes internal errors within the visual studio debugger in
some cases. Also debugging of static / global variabels is not possible
On Saturday, 25 May 2013 at 10:33:12 UTC, Vladimir Panteleev
wrote:
You don't need to do that to slice a string. I think you mean
to say that you need to decode each character if you want to
slice the string at the N-th code point? But this is exactly
what I'm trying to point out: how would
By extension,
template Foo[X, Y, Z @ X[Y], Y[Z]] { alias Y Foo; }
On 05/25/2013 05:56 AM, H. S. Teoh wrote:
On Fri, May 24, 2013 at 08:45:56PM -0700, Walter Bright wrote:
On 5/24/2013 7:16 PM, Manu wrote:
So when we define operators for u × v and a · b, or maybe n²? ;)
Oh, how I want to do that. But I still think the world hasn't
completely caught up with
Is this what you're looking for?
struct Foo(T)
{
static void bar() { writeln(general); }
}
struct Foo(T : A[B], A, B)
{
static void bar() { writeln(special); }
}
void main()
{
Foo!(int).bar(); // general
Foo!(int[int]).bar(); // special
}
No,
struct Foo(T) {
static void f() { writeln(general); }
}
struct Foo(T : A(B).alias C, A, B, C) {
static void f() { writeln(special); }
}
struct Bar(T) {
struct Baz {}
}
struct Baz(T : A(B), A, B) {
}
void main() {
Foo!(Bar!(int).Baz);
Baz!(Bar!(int));
}
Uneditable newsgroups. Simplest case.
struct Bar(T) {}
struct Foo(T : A(B), A, B) {
static void f() {}
}
void main() {
Foo!(Bar!(int)).f();
}
On Saturday, 25 May 2013 at 11:07:54 UTC, Joakim wrote:
If you want to split a string by ASCII whitespace (newlines,
tabs and spaces), it makes no difference whether the string is
in ASCII or UTF-8 - the code will behave correctly in either
case, variable-width-encodings regardless.
Except
On Saturday, 25 May 2013 at 12:13:42 UTC, Ahuzhgairl wrote:
Uneditable newsgroups. Simplest case.
struct Bar(T) {}
struct Foo(T : A(B), A, B) {
static void f() {}
}
void main() {
Foo!(Bar!(int)).f();
}
Two problems with that:
1. A(B) should be A!(B)
2. A won't bind to Bar because
2013/5/25 Ahuzhgairl bulletproofch...@gmail.com
Uneditable newsgroups. Simplest case.
struct Bar(T) {}
struct Foo(T : A(B), A, B) {
static void f() {}
}
void main() {
Foo!(Bar!(int)).f();
}
It would work.
struct Bar(T) {}
struct Foo(T : A!(B), alias A, B) { // 1, 2
On 5/25/13 3:33 AM, Joakim wrote:
On Saturday, 25 May 2013 at 01:58:41 UTC, Walter Bright wrote:
This is more a problem with the algorithms taking the easy way than a
problem with UTF-8. You can do all the string algorithms, including
regex, by working with the UTF-8 directly rather than
C++ example, works:
template class struct A;
template template class class X, class Y struct AXY {};
template class struct B;
int main() {
ABint a;
}
But the following does not work:
struct Foo {};
template class struct B { Foo x; }
template nontype P struct A;
template auto M, auto
On 5/25/13 5:08 AM, TommiT wrote:
I just tried out Sublime Text 2 and found it to be quite similar but
somewhat better than TextMate 2. And there's an improved D syntax
highlighter for it at: https://github.com/alexrp/st2-d
All the keywords seem to be there, indentation works etc.
Sublime Text
On Tuesday, 18 December 2012 at 13:33:03 UTC, Gor Gyolchanyan
wrote:
Good day, fellow D developers.
After spending much time figuring out how to make DMD work
fluently under
64-bit Windows 7 I've realized that this is not a trivial task
and lots of
people might have trouble with this, so I've
OK, you convinced me to try. But my SublimeText OSX
installation does not contain the D.tmPackage file described at
https://github.com/alexrp/st2-d. Where do I put it?
Thanks,
Andrei
ST2 and ST3 have built-in D Syntax highlighting.
ST3 now in the beta stage, but have improved mac os x
Where do I put it?
Thanks,
Andrei
http://docs.sublimetext.info/en/latest/extensibility/syntaxdefs.html
On 25.05.2013 15:03, Sébastien Kunz-Jacques kunzj...@yahoo.fr wrote:
On Tuesday, 18 December 2012 at 13:33:03 UTC, Gor Gyolchanyan wrote:
I hope I was helpful, because when I started to set up a development
environment under 64-bit Windows 7, I went through a lot of problems
to get
here and
On Saturday, 25 May 2013 at 12:43:42 UTC, Ahuzhgairl wrote:
C++ example, works:
template class struct A;
template template class class X, class Y struct AXY {};
template class struct B;
int main() {
ABint a;
}
As we've shown, you can do this in D. Instead of template
templates, you use
2013/5/25 Ahuzhgairl bulletproofch...@gmail.com
No,
struct Foo(T) {
static void f() { writeln(general); }
}
struct Foo(T : A(B).alias C, A, B, C) {
static void f() { writeln(special); }
}
struct Bar(T) {
struct Baz {}
}
struct Baz(T : A(B), A, B) {
}
void main() {
On Saturday, 25 May 2013 at 12:26:47 UTC, Vladimir Panteleev
wrote:
On Saturday, 25 May 2013 at 11:07:54 UTC, Joakim wrote:
If you want to split a string by ASCII whitespace (newlines,
tabs and spaces), it makes no difference whether the string
is in ASCII or UTF-8 - the code will behave
On Saturday, 25 May 2013 at 13:24:56 UTC, Rainer Schuetze wrote:
On 25.05.2013 15:03, Sébastien Kunz-Jacques
kunzj...@yahoo.fr wrote:
On Tuesday, 18 December 2012 at 13:33:03 UTC, Gor Gyolchanyan
wrote:
I hope I was helpful, because when I started to set up a
development
environment under
On Saturday, 25 May 2013 at 13:47:42 UTC, Joakim wrote:
On Saturday, 25 May 2013 at 12:26:47 UTC, Vladimir Panteleev
wrote:
On Saturday, 25 May 2013 at 11:07:54 UTC, Joakim wrote:
If you want to split a string by ASCII whitespace (newlines,
tabs and spaces), it makes no difference whether the
On Saturday, 25 May 2013 at 14:16:21 UTC, Peter Alexander wrote:
int countSpaces(const(char)* c)
{
int n = 0;
while (*c)
if (*c == ' ')
++n;
return n;
}
Oops. Missing a ++c in there, but I'm sure the point was made :-)
On Saturday, 25 May 2013 at 13:47:42 UTC, Joakim wrote:
On Saturday, 25 May 2013 at 12:26:47 UTC, Vladimir Panteleev
wrote:
On Saturday, 25 May 2013 at 11:07:54 UTC, Joakim wrote:
If you want to split a string by ASCII whitespace (newlines,
tabs and spaces), it makes no difference whether the
On Sat, May 25, 2013 at 03:47:41PM +0200, Joakim wrote:
On Saturday, 25 May 2013 at 12:26:47 UTC, Vladimir Panteleev wrote:
On Saturday, 25 May 2013 at 11:07:54 UTC, Joakim wrote:
If you want to split a string by ASCII whitespace (newlines,
tabs and spaces), it makes no difference whether the
On Saturday, 25 May 2013 at 14:18:32 UTC, Vladimir Panteleev
wrote:
On Saturday, 25 May 2013 at 13:47:42 UTC, Joakim wrote:
Are you sure _you_ understand it properly? Both encodings
have to check every single character to test for whitespace,
but the single-byte encoding simply has to load
Manu turkey...@gmail.com wrote in message
news:mailman.137.1369448229.13711.digitalmar...@puremagic.com...
One of the first, and best, decisions I made for D was it would be
Unicode
front to back.
Indeed, excellent decision!
So when we define operators for u × v and a · b, or maybe n²?
I suggest you check the XMLP library by Michael Rynn. I tried
XML processing with D, so I don't know how good the different
libraries are, but XMLP is on the review queue, which means
it's highly possible it will become Phobos' standard XML
library, and when that happens you will have an easy
On Saturday, 25 May 2013 at 10:46:05 UTC, Ahuzhgairl wrote:
Hi,
In D, the : in a template parameter list only binds to 1
parameter.
There is no way to specialize upon the entire template
parameter list.
Therefore you can't do much with the pattern matching and it's
not powerful.
Not a
25-May-2013 10:44, Joakim пишет:
On Friday, 24 May 2013 at 21:21:27 UTC, Dmitry Olshansky wrote:
You seem to think that not only UTF-8 is bad encoding but also one
unified encoding (code-space) is bad(?).
Yes, on the encoding, if it's a variable-length encoding like UTF-8, no,
on the code
25-May-2013 13:05, Joakim пишет:
On Saturday, 25 May 2013 at 08:42:46 UTC, Walter Bright wrote:
I think you stand alone in your desire to return to code pages.
Nobody is talking about going back to code pages. I'm talking about
going to single-byte encodings, which do not imply the problems
25-May-2013 12:58, Vladimir Panteleev пишет:
On Saturday, 25 May 2013 at 07:33:15 UTC, Joakim wrote:
This is more a problem with the algorithms taking the easy way than a
problem with UTF-8. You can do all the string algorithms, including
regex, by working with the UTF-8 directly rather than
On Saturday, 25 May 2013 at 08:07:42 UTC, Joakim wrote:
On Saturday, 25 May 2013 at 07:48:05 UTC, Diggory wrote:
I think you are a little confused about what unicode actually
is... Unicode has nothing to do with code pages and nobody
uses code pages any more except for compatibility with
Good afternoon, all,
I would still like to compile the D Lang Spec into EPUB (and
possibly other formats) but, as we discussed in these threads:
http://forum.dlang.org/thread/bsbdpjyjubfxvmecw...@forum.dlang.org
http://forum.dlang.org/thread/uzdngvjzexukbgkxd...@forum.dlang.org
having the D
I hasten to add that I don't mean to criticise the original
writers of the DLang Spec for writing it in DDoc macros. So far,
I've found the documentation fairly easy to follow (as plain
text) and so I don't want to lose any of that should the spec be
rewritten.
It's also possible (although,
On Saturday, 25 May 2013 at 17:03:43 UTC, Dmitry Olshansky wrote:
25-May-2013 10:44, Joakim пишет:
Yes, on the encoding, if it's a variable-length encoding like
UTF-8, no,
on the code space. I was originally going to title my post,
Why
Unicode? but I have no real problem with UCS, which
On Saturday, 25 May 2013 at 05:29:31 UTC, deadalnix wrote:
This is technically possible, but you said you make few
allocations. So with the tax on pointer write or the reference
counting, you'll pay a lot to collect very few garbages. I'm
not sure the tradeoff is worthwhile.
Incidentally,
░ⓌⓉⒻ░
╔╗░╔╗░╔╗╔╗╔╗░░
║║░║║░║║╚═╗╔═╝║╔═══╝░░
║║░║║░║║░░║║░░║╚═╗
║╚═╝╚═╝║╔╗║║╔╗║╔═╝╔╗░░
╚══╝╚╝╚╝╚╝╚╝░░╚╝░░
█░█░█░░▐░░▐░
█░█░█▐▀█▐▀█▐░█▐▀█▐▀█▐▀█░
█░█░█▐▄█▐▄█▐▄▀▐▄█▐░█▐░█░
█▄█▄█▐▄▄▐▄▄▐░█▐▄▄▐░█▐▄█░
--jm
limited success of UTF-8
Becoming the de-facto standard encoding EVERYWERE except for
windows which uses UTF-16 is hardly a failure...
I really don't understand your hatred for UTF-8 - it's simple to
decode and encode, fast and space-efficient. Fixed width
encodings are not inherently fast,
On Saturday, 25 May 2013 at 16:27:59 UTC, deadalnix wrote:
Hi, I obviously don't know D that much, but I assume I do.
[..snip..]
chuckle
+1
25-May-2013 22:26, Joakim пишет:
On Saturday, 25 May 2013 at 17:03:43 UTC, Dmitry Olshansky wrote:
25-May-2013 10:44, Joakim пишет:
Yes, on the encoding, if it's a variable-length encoding like UTF-8, no,
on the code space. I was originally going to title my post, Why
Unicode? but I have no
On Saturday, 25 May 2013 at 18:09:26 UTC, Diggory wrote:
On Saturday, 25 May 2013 at 08:07:42 UTC, Joakim wrote:
On Saturday, 25 May 2013 at 07:48:05 UTC, Diggory wrote:
I think you are a little confused about what unicode actually
is... Unicode has nothing to do with code pages and nobody
On May 24, 2013, at 3:50 PM, Luís.Marques
luismarq...@gmail.com@puremagic.com wrote:
On Friday, 24 May 2013 at 21:49:48 UTC, Sean Kelly wrote:
It should work for any type that Variant can represent. I know Variant has
trouble with immutable however. Have you tried shared? std.concurrency
On 5/25/2013 5:43 AM, Andrei Alexandrescu wrote:
On 5/25/13 3:33 AM, Joakim wrote:
On Saturday, 25 May 2013 at 01:58:41 UTC, Walter Bright wrote:
This is more a problem with the algorithms taking the easy way than a
problem with UTF-8. You can do all the string algorithms, including
regex, by
On 5/25/2013 1:07 AM, Joakim wrote:
The vast majority of non-english alphabets in UCS can be encoded in a single
byte. It is your exceptions that are not relevant.
I suspect the Chinese, Koreans, and Japanese would take exception to being
called irrelevant.
Good luck with your scheme that
Kenji,
Thank you much for the '.C' alias support, Amazed to see there
could be some action so quick!
Could we please look at the nontype-as-primary-template?
How can we deduce all of the dependent types from a non-type
template parameter, if it's the only parameter of the primary
template?
On Saturday, 25 May 2013 at 19:02:43 UTC, Joakim wrote:
On Saturday, 25 May 2013 at 18:09:26 UTC, Diggory wrote:
On Saturday, 25 May 2013 at 08:07:42 UTC, Joakim wrote:
On Saturday, 25 May 2013 at 07:48:05 UTC, Diggory wrote:
I think you are a little confused about what unicode
actually is...
On Saturday, 25 May 2013 at 19:03:53 UTC, Dmitry Olshansky wrote:
You can map a codepage to a subset of UCS :)
That's what they do internally anyway.
If I take you right you propose to define string as a header
that denotes a set of windows in code space? I still fail to
see how that would
On 5/25/13 12:27 PM, deadalnix wrote:
Hi, I obviously don't know D that much, but I assume I do.
I have this feature that I can't even show a working example that exists
in C++. I also can't come up with any use case, but I know this is
mandatory to have.
As I assume I know D well enough, I
25-May-2013 23:51, Joakim пишет:
On Saturday, 25 May 2013 at 19:03:53 UTC, Dmitry Olshansky wrote:
You can map a codepage to a subset of UCS :)
That's what they do internally anyway.
If I take you right you propose to define string as a header that
denotes a set of windows in code space? I
On Saturday, 25 May 2013 at 19:30:25 UTC, Walter Bright wrote:
On the other hand, Joakim even admits his single byte encoding
is variable length, as otherwise he simply dismisses the rarely
used (!) Chinese, Japanese, and Korean languages, as well as
any text that contains words from more than
On Saturday, 25 May 2013 at 19:51:43 UTC, Joakim wrote:
On Saturday, 25 May 2013 at 19:03:53 UTC, Dmitry Olshansky
wrote:
You can map a codepage to a subset of UCS :)
That's what they do internally anyway.
If I take you right you propose to define string as a header
that denotes a set of
On Sat, May 25, 2013 at 10:07:41AM +0200, Joakim wrote:
[...]
The vast majority of non-english alphabets in UCS can be encoded in
a single byte. It is your exceptions that are not relevant.
I'll have you know that Chinese, Korean, and Japanese account for a
significant percentage of the
On Saturday, 25 May 2013 at 14:58:02 UTC, Joakim wrote:
On Saturday, 25 May 2013 at 14:16:21 UTC, Peter Alexander wrote:
I suggest you read up on UTF-8. You really don't understand
it. There is no need to decode, you just treat the UTF-8
string as if it is an ASCII string.
Not being aware of
On Sat, May 25, 2013 at 09:51:42PM +0200, Joakim wrote:
On Saturday, 25 May 2013 at 19:03:53 UTC, Dmitry Olshansky wrote:
If I take you right you propose to define string as a header that
denotes a set of windows in code space? I still fail to see how
that would scale see below.
Something
On 5/25/2013 1:03 PM, Joakim wrote:
On Saturday, 25 May 2013 at 19:30:25 UTC, Walter Bright wrote:
On the other hand, Joakim even admits his single byte encoding is variable
length, as otherwise he simply dismisses the rarely used (!) Chinese,
Japanese, and Korean languages, as well as any text
On 5/25/2013 12:51 PM, Joakim wrote:
For a multi-language string encoding, the header would
contain a single byte for every language used in the string, along with multiple
index bytes to signify the start and finish of every run of single-language
characters in the string. So, a list of
On 5/25/2013 2:51 PM, Walter Bright wrote:
On 5/25/2013 12:51 PM, Joakim wrote:
For a multi-language string encoding, the header would
contain a single byte for every language used in the string, along with multiple
index bytes to signify the start and finish of every run of single-language
On Saturday, 25 May 2013 at 20:03:59 UTC, Joakim wrote:
I have noted from the beginning that these large alphabets have
to be encoded to two bytes, so it is not a true constant-width
encoding if you are mixing one of those languages into a
single-byte encoded string. But this variable length
On Saturday, 25 May 2013 at 12:56:02 UTC, Andrei Alexandrescu
wrote:
OK, you convinced me to try. But my SublimeText OSX
installation does not contain the D.tmPackage file described at
https://github.com/alexrp/st2-d. Where do I put it?
Thanks,
Andrei
I found it through: Sublime Text 2 -
On Saturday, May 25, 2013 01:42:20 Walter Bright wrote:
On 5/25/2013 12:33 AM, Joakim wrote:
At what cost? Most programmers completely punt on unicode, because they
just don't want to deal with the complexity. Perhaps you can deal with it
and don't mind the performance loss, but I suspect
On 5/25/13 7:01 PM, TommiT wrote:
On Saturday, 25 May 2013 at 12:56:02 UTC, Andrei Alexandrescu wrote:
OK, you convinced me to try. But my SublimeText OSX installation does
not contain the D.tmPackage file described at
https://github.com/alexrp/st2-d. Where do I put it?
Thanks,
Andrei
I
On 05/24/2013 04:33 PM, Manu wrote:
But anyway, after fixing the obvious Phobos offenders, another huge
step would be to get TempAlloc into druntime and used wherever
possible in Phobos.
How does that work?
One pattern I've used a lot is, since we have a regular 60hz timeslice
and
I think this have not been posted yet around here but might be interesting
to the D community as it is actually criticizing several languages
including D but with an interesting aproach:
http://sebastiansylvan.wordpress.com/2013/05/25/language-design-deal-breakers/
Joel Lamotte
On Saturday, May 25, 2013 20:10:53 Borden wrote:
Good afternoon, all,
I would still like to compile the D Lang Spec into EPUB (and
possibly other formats) but, as we discussed in these threads:
http://forum.dlang.org/thread/bsbdpjyjubfxvmecw...@forum.dlang.org
On Saturday, 25 May 2013 at 23:18:22 UTC, Andrei Alexandrescu
wrote:
On 5/25/13 7:01 PM, TommiT wrote:
On Saturday, 25 May 2013 at 12:56:02 UTC, Andrei Alexandrescu
wrote:
OK, you convinced me to try. But my SublimeText OSX
installation does
not contain the D.tmPackage file described at
On Sunday, May 26, 2013 00:50:28 Klaim - Joël Lamotte wrote:
I think this have not been posted yet around here but might be interesting
to the D community as it is actually criticizing several languages
including D but with an interesting aproach:
A)
Requiring a construct such as Checked!int is too complicated for the user
in general as it requires a lot of code change from the user. It may be
useful in certain cases but overflow bugs will crop up in unexpected places.
B)
To help finding such bugs, introduce a special version identifier
On 05/26/2013 01:39 AM, Jonathan M Davis wrote:
On Sunday, May 26, 2013 00:50:28 Klaim - Joël Lamotte wrote:
I think this have not been posted yet around here but might be interesting
to the D community as it is actually criticizing several languages
including D but with an interesting aproach:
And, to make caseS and default of a switch indent to the same
column as the switch, I made a small modification to the file
~/Library/Application Support/Sublime Text
2/Packages/D/Indentation Rules.tmPreferences and, again deleted
the Indentation Rules.tmPreferences.cache file and restarted
On Sunday, May 26, 2013 01:54:36 Timon Gehr wrote:
On 05/26/2013 01:39 AM, Jonathan M Davis wrote:
On Sunday, May 26, 2013 00:50:28 Klaim - Joël Lamotte wrote:
I think this have not been posted yet around here but might be
interesting
to the D community as it is actually criticizing
On 5/25/2013 4:54 PM, Timon Gehr wrote:
On 05/26/2013 01:39 AM, Jonathan M Davis wrote:
On Sunday, May 26, 2013 00:50:28 Klaim - Joël Lamotte wrote:
I think this have not been posted yet around here but might be interesting
to the D community as it is actually criticizing several languages
On 5/25/13 2:16 PM, Borden wrote:
I hasten to add that I don't mean to criticise the original writers of
the DLang Spec for writing it in DDoc macros. So far, I've found the
documentation fairly easy to follow (as plain text) and so I don't want
to lose any of that should the spec be rewritten.
1 - 100 of 187 matches
Mail list logo
