On Sunday, February 24, 2013 06:21:05 Andrej Mitrovic wrote:
> On 2/24/13, Jonathan M Davis wrote:
> > Because the compiler doesn't general deal on the level of code points. It
> > deals with code units, and it doesn't generally treat strings as being
> > special
> > at all. So, you can't compare
On 2/24/13, Jonathan M Davis wrote:
> Because the compiler doesn't general deal on the level of code points. It
> deals with code units, and it doesn't generally treat strings as being
> special
> at all. So, you can't compare string and dstring any more than you can
> compare
> ubye[] and uint[].
On Sunday, February 24, 2013 05:18:18 Andrej Mitrovic wrote:
> On 2/24/13, Jonathan M Davis wrote:
> > strings and dstrings aren't comparable.
>
> Why aren't they? They're just different encodings of UTF, I'd expect
> Phobos to support comparing UTF8/UTF16/UTF32 against each other.
Because the c
On 2/24/13, Jonathan M Davis wrote:
> strings and dstrings aren't comparable.
Why aren't they? They're just different encodings of UTF, I'd expect
Phobos to support comparing UTF8/UTF16/UTF32 against each other.
On Sat, 23 Feb 2013 22:39:55 -0500, Andrej Mitrovic
wrote:
It seems this doesn't work:
import std.algorithm;
auto b1 = qual(["foo"d], ["foo"]);
auto b2 = equal(["foo"d.dup], ["foo"]);
It's due to a constraint failure:
is(typeof(r1.front == r2.front))
The first call is:
immutable(dchar)[]
s
On Sunday, February 24, 2013 04:39:55 Andrej Mitrovic wrote:
> It seems this doesn't work:
>
> import std.algorithm;
> auto b1 = qual(["foo"d], ["foo"]);
> auto b2 = equal(["foo"d.dup], ["foo"]);
>
> It's due to a constraint failure:
> is(typeof(r1.front == r2.front))
>
> The first call is:
> im
On 02/23/2013 06:30 PM, Jesse Phillips wrote:
On Saturday, 23 February 2013 at 19:07:31 UTC, Charles Hixson wrote:
What actually brought this up is that I've gotten so disgusted with
ddoc that I was looking for pretty much ANY alternative.
ah, then Tex isn't what you want. As for improving DDO
On Saturday, 23 February 2013 at 19:07:31 UTC, Charles Hixson
wrote:
What actually brought this up is that I've gotten so disgusted
with ddoc that I was looking for pretty much ANY alternative.
ah, then Tex isn't what you want. As for improving DDOC several
attempts have been made. CandyDoc
On Wednesday, 13 February 2013 at 15:53:44 UTC, Andrea Fontana
wrote:
Why Appender has no ~ operator itself?
auto app = appender!string();
app.put("a"); // why not app ~= "a"?
Because Appender is an output range, using ~= will mean your code
will not work with other output ranges.
On Sat, 23 Feb 2013 17:09:06 -0800, Ali Çehreli wrote:
> The following is minimized code, which does not have any compilation
> errors:
>
> [snip]
>
> You can replace my stub functions with your code to help identify the
> problem.
>
> Ali
Thanks Ali; much appreciated.
--
Lee
H. S. Teoh:
AFAIK, x..y syntax only works in foreach and in array slicing.
Sadly.
Bye,
bearophile
On 02/23/2013 03:23 PM, Lee Braiden wrote:
Hi all,
I'm defining a template class with a static method, and adding a call to
that to a taskpool. However, when I run it, I get a "null this" error
from parallelism.d.
Here's the minimised code:
class Population(GeneType)
{
alias Populatio
On Wed, 13 Feb 2013 17:00:39 +0100, bearophile wrote:
> Andrea Fontana:
>> Why Appender has no ~ operator itself?
>>
>> auto app = appender!string(); app.put("a"); // why not app ~= "a"?
>
> Now it's in GIT head.
That's a nice touch. Good idea, Andrea :)
--
Lee
On Sun, 17 Feb 2013 10:58:57 -0800, Charles Hixson wrote:
> Thank you. Since "volatile", IIUC, is suppose to mean "This think can
> change without warning, and for no reason that you'll be able to see.",
It ALSO means, "This can be read by other processes / devices at any
time, so don't assume y
On Sun, Feb 24, 2013 at 12:04:35AM +, Lee Braiden wrote:
> Just a quick conceptual question: why doesn't the following work?
>
> foreach(i ; parallel(1 .. 11))
> {
> ...
> }
>
> I would have expected 1 .. 10 to give me a range, and parallel to work
> with that. Does 1 .. 11 ONLY work as
Just a quick conceptual question: why doesn't the following work?
foreach(i ; parallel(1 .. 11))
{
...
}
I would have expected 1 .. 10 to give me a range, and parallel to work
with that. Does 1 .. 11 ONLY work as part of the foreach() syntax?
If not, is there some sort of range generator h
On Mon, 18 Feb 2013 23:14:54 +0100, Andrej Mitrovic wrote:
> http://dlang.org/template.html#TemplateThisParameter
>
> That's hardly a descriptive example, so in what context is the feature
> useful? Some code snippets would be welcome so we can update the page
> with a nicer and more useful examp
On Saturday, 23 February 2013 at 17:01:48 UTC, Damian wrote:
Ok signals work fine, until I use them in a descendant class.
Snippet:
-
import std.signals;
class ClassA
{
public mixin Signal!(int) addNumber1;
}
class ClassB : ClassA
{
public mixin Signal!(int) add
On Tue, 19 Feb 2013 22:41:04 +0100, deed wrote:
>> D code DLLs called by D code are heavly broken. Don't expect it to
>> work.
>
> Any solid workarounds?
I don't really know the issues with this, but I do know that Walter was
just saying in his latest talk that fixing this particular issue will
Hi all,
I'm defining a template class with a static method, and adding a call to
that to a taskpool. However, when I run it, I get a "null this" error
from parallelism.d.
Here's the minimised code:
class Population(GeneType)
{
alias Population!(GeneType) ThisType;
static void
On 02/23/2013 02:44 AM, Lubos Pintes wrote:
> Maybe I don't understand this example fully,
It is one way of adding information to an exception. (There are other ways.)
> but where is a "try"
> statement?
It is not needed here because the requirement is achieved by the
destructor of LineInfo.
On 02/23/2013 06:11 AM, Mike Parker wrote:
On Saturday, 23 February 2013 at 12:59:44 UTC, deed wrote:
as there is no randomness involved, only the possibility to access by
index.
"random access" is exactly the name this sort of behavior has always
had. It doesn't mean random as in /according t
On 02/22/2013 08:59 PM, Jesse Phillips wrote:
Nope, removed. While not the same and may not do anything that you are
considering.
This was made to compile listings and then put the output of compiler
and run into a new tex file.
https://github.com/JesseKPhillips/listings-dlang-extractor
What a
On Saturday, 23 February 2013 at 12:59:44 UTC, deed wrote:
as there is no randomness involved, only the possibility to
access by index.
"random access" is exactly the name this sort of behavior has
always had. It doesn't mean random as in /according to chance/,
but random as in non-sequential
as there is no randomness involved, only the possibility to
access by index.
Maybe I don't understand this example fully, but where is a "try" statement?
The to!int may throw...
Dňa 29. 1. 2013 22:53 Ali Çehreli wrote / napísal(a):
On 01/29/2013 12:32 PM, Vladimir Panteleev wrote:
> I would like to add some information to any exceptions thrown inside the
> loop's body
26 matches
Mail list logo
