[Issue 14601] pthread functions aren't marked @nogc

https://issues.dlang.org/show_bug.cgi?id=14601 Ender KaShae changed: What|Removed |Added CC||astrotha...@gmail.com

Re: Asio Bindings?

On Thursday, 2 June 2016 at 04:02:36 UTC, Pie? wrote: Does anyone know if there is any Asio bindings or direct D available that allows for IO? Check out vibe.d: https://vibed.org/ - it includes a fairly complete implementation of asynchronous I/O, among other things.

Re: Dealing with Autodecode

On 6/1/2016 8:51 PM, Adam D. Ruppe wrote: On Wednesday, 1 June 2016 at 02:36:15 UTC, Walter Bright wrote: PRs please! https://github.com/dlang/phobos/pull/4384 You'll notice it is closed. Now, that one wasn't meant to be merged anyway, but Andrei seems to have zero interest in actually

Re: D Profile Viewer

I've updated the d-profile-viewer. It now supports identifiers that are not mangles - are these 'extern "C"'? Its on dub: dub fetch d-profile-viewer Its on bitbucket: https://bitbucket.org/andrewtrotman/d-profile-viewer Thanks go to those who identified the bugs. Andrew.

Asio Bindings?

Does anyone know if there is any Asio bindings or direct D available that allows for IO?

Re: adamdruppe: Drawing scaled image

On Thursday, 2 June 2016 at 03:37:01 UTC, Adam D. Ruppe wrote: On Thursday, 2 June 2016 at 03:19:20 UTC, Pie? wrote: I'm curious about how to draw a scaled image. There's a few general options: 1) Scale it yourself in-memory then draw. This is a pain, I don't think my public libraries have

Re: Dealing with Autodecode

On Wednesday, 1 June 2016 at 02:36:15 UTC, Walter Bright wrote: PRs please! https://github.com/dlang/phobos/pull/4384 You'll notice it is closed. Now, that one wasn't meant to be merged anyway, but Andrei seems to have zero interest in actually accepting the change. That doesn't encourage

Re: adamdruppe: Drawing scaled image

On Thursday, 2 June 2016 at 03:19:20 UTC, Pie? wrote: I'm curious about how to draw a scaled image. There's a few general options: 1) Scale it yourself in-memory then draw. This is a pain, I don't think my public libraries have a scale method 2) If on MS Windows, you can resize the

adamdruppe: Drawing scaled image

I found your git hub and tried simpledisplay and png. I had virtually no problems getting them working from the get go! Thanks for your hard work!!! You deserve a cookie, or a million bucks! I'm curious about how to draw a scaled image. I would like to have a "global" scale for my image

Re: Free the DMD backend

On Tuesday, 31 May 2016 at 20:18:34 UTC, default0 wrote: I have no idea how licensing would work in that regard but considering that DMDs backend is actively maintained and may eventually even be ported to D, wouldn't it at some point differ enough from Symantecs "original" backend to simply

Re: Free the DMD backend

On Wednesday, 1 June 2016 at 01:26:53 UTC, Eugene Wissner wrote: On Tuesday, 31 May 2016 at 20:12:33 UTC, Russel Winder wrote: On Tue, 2016-05-31 at 10:09 +, Atila Neves via Digitalmars-d wrote:  […] No, no, no, no. We had LDC be the default already on Arch Linux for a while and it was a

Re: Can I get a more in-depth guide about the inline assembler?

On Thursday, 2 June 2016 at 00:52:48 UTC, ZILtoid1991 wrote: On Thursday, 2 June 2016 at 00:51:15 UTC, ZILtoid1991 wrote: I could get the code working with a bug after replacing pmulhuw with pmullw, but due to integer overflow I get a glitched image. I try to get around the fact that pmulhuw

Re: Can I get a more in-depth guide about the inline assembler?

On Thursday, 2 June 2016 at 00:51:15 UTC, ZILtoid1991 wrote: On Wednesday, 1 June 2016 at 23:35:40 UTC, Era Scarecrow wrote: On Wednesday, 1 June 2016 at 23:23:49 UTC, ZILtoid1991 wrote: I could get the code working with a bug after replacing pmulhuw with pmullw, but due to integer overflow

Re: Quite sure a simple basic problem...

On Thursday, 2 June 2016 at 00:37:58 UTC, WhatMeWorry wrote: I've got a fairly complex D project (25+ modules) that has grown haphazardly over time. So it is not well designed. But I want to get the thing fully ported before refining the code. (that's called refactoring, I believe?) Anyway,

Re: Can I get a more in-depth guide about the inline assembler?

On Wednesday, 1 June 2016 at 23:35:40 UTC, Era Scarecrow wrote: On Wednesday, 1 June 2016 at 23:23:49 UTC, ZILtoid1991 wrote: After some debugging, I found out that the p pointer becomes null at the end instead of pointing to a value. I have no experience with using in-line assemblers

Quite sure a simple basic problem...

I've got a fairly complex D project (25+ modules) that has grown haphazardly over time. So it is not well designed. But I want to get the thing fully ported before refining the code. (that's called refactoring, I believe?) Anyway, there is a new module called audio.d which which has all the

Re: Transient ranges

On 6/1/16 10:05 AM, Patrick Schluter wrote: On Tuesday, 31 May 2016 at 12:42:23 UTC, Steven Schveighoffer wrote: There are 2 main issues with FILE *: 1) it does not provide buffer access, so you must rely on things like getline if they exist. But these have their own problems (i.e. do not

Re: Transient ranges

On 6/1/16 8:49 AM, Joseph Rushton Wakeling wrote: On Tuesday, 31 May 2016 at 18:31:05 UTC, Steven Schveighoffer wrote: On 5/31/16 11:45 AM, Jonathan M Davis via Digitalmars-d wrote: On Monday, May 30, 2016 09:57:29 H. S. Teoh via Digitalmars-d wrote: I'd argue that range-based generic code

Re: Unittests run without error when done individually, but when unittesting the package some fail

On Wednesday, June 01, 2016 23:58:52 pineapple via Digitalmars-d-learn wrote: > How this could possibly be happening is confounding me and I have > no idea if it's something I missed or some contrived compiler bug. > > This is the package.d that previously I've compiled with unittest > every so

Re: Dealing with Autodecode

On Wednesday, 1 June 2016 at 11:42:06 UTC, Seb wrote: On Wednesday, 1 June 2016 at 02:39:55 UTC, Nick Sabalausky wrote: On 05/31/2016 09:36 PM, Adam D. Ruppe wrote: version(string_migration) deprecated void popFront(T)(ref T t) if(isSomeString!T) { static assert(0, "this is crap, fix your

Unittests run without error when done individually, but when unittesting the package some fail

How this could possibly be happening is confounding me and I have no idea if it's something I missed or some contrived compiler bug. This is the package.d that previously I've compiled with unittest every so often as a way of doing regression testing -

Re: Can I get a more in-depth guide about the inline assembler?

On Wednesday, 1 June 2016 at 23:23:49 UTC, ZILtoid1991 wrote: After some debugging, I found out that the p pointer becomes null at the end instead of pointing to a value. I have no experience with using in-line assemblers (although I made a few Hello World programs for MS-Dos with a

Can I get a more in-depth guide about the inline assembler?

Here's the assembly code for my alpha-blending routine: ubyte[4] src = *cast(ubyte[4]*)(palette.ptr + 4 * *c); ubyte[4] *p = cast(ubyte[4]*)(workpad + (offsetX + x)*4 + offsetY); asm{//moving the values to their destinations movdMM0, p; movdMM1, src; movqMM5, alpha; movqMM7,

Re: The Case Against Autodecode

On 06/01/2016 06:09 PM, ZombineDev wrote: Regardless of how different people may call it, it's not what this thread is about. Yes, definitely - but then again we can't after each invalidated claim to go "yeah well but that other point stands". Deprecating front, popFront and empty for

Re: The Case Against Autodecode

On Wednesday, 1 June 2016 at 19:52:01 UTC, Andrei Alexandrescu wrote: On 06/01/2016 03:07 PM, ZombineDev wrote: This is not autodecoding. There is nothing auto-magic w.r.t. strings in plain foreach. I understand where you're coming from, but it actually is autodecoding. Consider: byte[]

Re: The Case Against Autodecode

On 06/01/2016 05:30 PM, Jack Stouffer wrote: On Wednesday, 1 June 2016 at 19:52:01 UTC, Andrei Alexandrescu wrote: foreach (dchar x; a) {} The latter two do autodecoding, not coversion as the rest of the language. This seems to be a miscommunication with semantics. This is not auto-decoding

[Issue 12721] Unresolved Symbols when Linking

https://issues.dlang.org/show_bug.cgi?id=12721 Jon changed: What|Removed |Added CC||jonfand...@gmail.com ---

Re: RCString

On 06/01/2016 05:03 PM, Timon Gehr wrote: The small string optimization also works for GC-allocated strings. Why do I always want to use RCString instead of the corresponding GCString? (Also, the same approach can be applied to other arrays with value semantics.) Point taken, thanks. Mine was

Re: Code security: "auto" / Reason for errors

On Wednesday, 1 June 2016 at 14:52:29 UTC, John Nixon wrote: On Wednesday, 2 March 2016 at 21:37:56 UTC, Steven Schveighoffer wrote: Pointer copying is inherent in D. Everything is done at the "head", deep copies are never implicit. This is a C-like language, so one must expect this kind of

Re: Speed up `dub`.

Hahahaa. Who could possibly think that `build.sh` builds dub in debug mode? With -release -O -inline -m64 it runs 5 times faster : P. It made my day...

Re: The Case Against Autodecode

On Wednesday, 1 June 2016 at 19:52:01 UTC, Andrei Alexandrescu wrote: foreach (dchar x; a) {} The latter two do autodecoding, not coversion as the rest of the language. This seems to be a miscommunication with semantics. This is not auto-decoding at all; you're decoding, but there is nothing

Re: Code security: "auto" / Reason for errors

On Wednesday, 1 June 2016 at 15:56:24 UTC, Kagamin wrote: Value-type containers are planned for phobos, but not done yet. Thank you for this info. This is probably what I want, meanwhile I’ll try to work round it. If you have any indication of the timing it might be useful.

Re: Code security: "auto" / Reason for errors

On 01.06.2016 17:34, deadalnix wrote: On Wednesday, 2 March 2016 at 19:42:02 UTC, Ozan wrote: Hi I despair of "auto var1 = var2"for arrays. Isn't it a open door for errors. Example import std.stdio; void main() { int[] a; foreach(i; 0..10) a ~= i; auto b = a; // correct dlang

RCString

On 01.06.2016 22:43, Andrei Alexandrescu wrote: On 06/01/2016 04:28 PM, Timon Gehr wrote: On 01.06.2016 17:30, Andrei Alexandrescu wrote: On 06/01/2016 11:24 AM, Jonathan M Davis via Digitalmars-d wrote: It seems more like RCString is an optimization for certain types of programs than what

Re: Creating a "fixed-range int" with opDispatch and/or alias this?

On Wednesday, 1 June 2016 at 19:59:51 UTC, Mark Isaacson wrote: FWIW, the fixed range int part of this question is just an example, I'm mostly just interested in whether this idea is possible without a lot of bloat/duplication. I suspect not.. Here's how std.typecons.Proxy is doing it:

Re: Dealing with Autodecode

On 06/01/2016 04:28 PM, Timon Gehr wrote: On 01.06.2016 17:30, Andrei Alexandrescu wrote: On 06/01/2016 11:24 AM, Jonathan M Davis via Digitalmars-d wrote: It seems more like RCString is an optimization for certain types of programs than what you'd want to use by default. You'll always want

Re: Using referenceCounters

On Wednesday, 1 June 2016 at 18:14:33 UTC, Begah wrote: I started using reference counters for my assets in my application : - Images - Models - For my resource manager I started out with something similar to what you're describing, but I eventually changed the design which turned

Re: Interest in Paris area D meetups?

On Wednesday, 1 June 2016 at 19:25:13 UTC, Claude wrote: On Wednesday, 18 May 2016 at 15:05:21 UTC, Guillaume Chatelet wrote: I got inspired by Steven's thread :) Anyone in Paris interested in D meetups? Sorry for the later reply, but yes, I'd be interested by a meetup in Paris. Anyone else?

Re: Dealing with Autodecode

On 01.06.2016 17:30, Andrei Alexandrescu wrote: On 06/01/2016 11:24 AM, Jonathan M Davis via Digitalmars-d wrote: It seems more like RCString is an optimization for certain types of programs than what you'd want to use by default. You'll always want to use it. The small string optimization

Creating a "fixed-range int" with opDispatch and/or alias this?

I'm trying to create a type that for all intents and purposes behaves exactly like an int except that it limits its values to be within a certain range [a,b]. Theoretically, I would think this looks something like: struct FixedRangeInt { this(int min, int max, int value=0) { this.min =

Re: The Case Against Autodecode

On 06/01/2016 03:07 PM, ZombineDev wrote: This is not autodecoding. There is nothing auto-magic w.r.t. strings in plain foreach. I understand where you're coming from, but it actually is autodecoding. Consider: byte[] a; foreach (byte x; a) {} foreach (short x; a) {} foreach (int x; a) {}

Re: Interest in Paris area D meetups?

On Wednesday, 18 May 2016 at 15:05:21 UTC, Guillaume Chatelet wrote: I got inspired by Steven's thread :) Anyone in Paris interested in D meetups? Sorry for the later reply, but yes, I'd be interested by a meetup in Paris. Anyone else?

Re: A ready to use Vulkan triangle example for D

I now have initial window resizing added to your example: https://github.com/Manuel-Koenig/VulkanTriangleD It's still pretty much your code, but I structured it into several functions. Window resizing does work in the sense that the triangle gets stretched and redrawn, but the validation layer

Re: Is there any overhead iterating over a pointer using a slice?

On Tuesday, 31 May 2016 at 20:52:20 UTC, Johan Engelen wrote: On Tuesday, 31 May 2016 at 18:55:18 UTC, Gary Willoughby wrote: If I have a pointer and iterate over it using a slice, like this: T* foo = foreach (element; foo[0 .. length]) { ...

Re: The Case Against Autodecode

On Wednesday, 1 June 2016 at 19:07:26 UTC, ZombineDev wrote: On Wednesday, 1 June 2016 at 17:57:15 UTC, Andrei Alexandrescu wrote: On 06/01/2016 01:35 PM, ZombineDev wrote: On Tuesday, 31 May 2016 at 19:33:03 UTC, Andrei Alexandrescu wrote: On 05/31/2016 02:46 PM, Timon Gehr wrote: On

Re: The Case Against Autodecode

On Wednesday, 1 June 2016 at 17:57:15 UTC, Andrei Alexandrescu wrote: On 06/01/2016 01:35 PM, ZombineDev wrote: On Tuesday, 31 May 2016 at 19:33:03 UTC, Andrei Alexandrescu wrote: On 05/31/2016 02:46 PM, Timon Gehr wrote: On 31.05.2016 20:30, Andrei Alexandrescu wrote: D's Phobos'

Re: Calling C++ code with pointer** argument

On Wednesday, 1 June 2016 at 16:16:26 UTC, Kagamin wrote: Can you declare it as const char*const* one the C++ side? Just to state the problem clearly, D's const is transitive, C++ it is not. C linkage doesn't care about const, so you can specify it however you want. In C++ the const is

Re: Using referenceCounters

I can see two option but neither of them is really portable : I can set _store public in std.typecons or i could create a setter method. Neither of these options is portable because i need to directly edit the librarie's source code so i can't jump from one computer to the next without having

[Issue 16107] [ICE] - Internal error: backend/cgcod.c 2297

https://issues.dlang.org/show_bug.cgi?id=16107 --- Comment #3 from b2.t...@gmx.com --- (In reply to ag0aep6g from comment #2) > Reduced further: > > > bool check() > { > bool result = false; > > result |= false; // result = result | ... : OK > if (result) goto ret; //

Re: [OT] Effect of UTF-8 on 2G connections

On Wednesday, 1 June 2016 at 16:45:04 UTC, Joakim wrote: On Wednesday, 1 June 2016 at 15:02:33 UTC, Wyatt wrote: It's not hard. I think a lot of us remember when a 14.4 modem was cutting-edge. Well, then apparently you're unaware of how bloated web pages are nowadays. It used to take me

Re: The Case Against Autodecode

On Wednesday, 1 June 2016 at 17:57:15 UTC, Andrei Alexandrescu wrote: Try typing the iteration variable with "dchar". -- Andrei Or you can type it as wchar... But important to note: that's opt in, not automatic.

Using referenceCounters

I started using reference counters for my assets in my application : - Images - Models - Such as : alias ModelType = RefCounted!Model; struct Model { static ModelType create(Mesh mesh, Shader shader) { ModelType model = ModelType(); model.mesh

Re: The Case Against Autodecode

On 06/01/2016 01:35 PM, ZombineDev wrote: On Tuesday, 31 May 2016 at 19:33:03 UTC, Andrei Alexandrescu wrote: On 05/31/2016 02:46 PM, Timon Gehr wrote: On 31.05.2016 20:30, Andrei Alexandrescu wrote: D's Phobos' foreach, too. -- Andrei Incorrect. https://dpaste.dzfl.pl/ba7a65d59534

Re: The Case Against Autodecode

On Tuesday, 31 May 2016 at 19:33:03 UTC, Andrei Alexandrescu wrote: On 05/31/2016 02:46 PM, Timon Gehr wrote: On 31.05.2016 20:30, Andrei Alexandrescu wrote: D's Phobos' foreach, too. -- Andrei Incorrect. https://dpaste.dzfl.pl/ba7a65d59534

Re: The Case Against Autodecode

On 06/01/2016 12:41 PM, Nick Sabalausky wrote: As has been explained countless times already, code points are a non-1:1 internal representation of graphemes. Code points don't exist for their own sake, their entire existence is purely as a way to encode graphemes. Of course, thank you.

Re: [OT] The Case Against... Unicode?

On Wednesday, 1 June 2016 at 16:26:36 UTC, deadalnix wrote: On Wednesday, 1 June 2016 at 16:15:15 UTC, Patrick Schluter wrote: What Joakim does not understand, is that there are huge, huge quantities of documents that are multi-lingual. That should be obvious to anyone living outside the USA.

[Issue 9114] Can't call varadic template function with partly specified template parameters

https://issues.dlang.org/show_bug.cgi?id=9114 --- Comment #2 from Andrej Mitrovic --- Here's another workaround, where you can simply declare an alias in your code via `alias FixedForward!(target_func) fixed_func` and use it regularly. - import tango.core.Traits;

Re: [OT] The Case Against... Unicode?

On 06/01/2016 12:26 PM, deadalnix wrote: On Wednesday, 1 June 2016 at 16:15:15 UTC, Patrick Schluter wrote: What Joakim does not understand, is that there are huge, huge quantities of documents that are multi-lingual. That should be obvious to anyone living outside the USA. Or anyone in

Re: [OT] The Case Against... Unicode?

On Wednesday, 1 June 2016 at 15:02:33 UTC, Wyatt wrote: If you have to deal with delivering the fastest possible i18n at GSM data rates, well, that's a tough problem and it sounds like you might need to do something pretty special. Turning the entire ecosystem into your special case is not the

Re: [OT] Effect of UTF-8 on 2G connections

On Wednesday, 1 June 2016 at 14:58:47 UTC, Marco Leise wrote: Am Wed, 01 Jun 2016 13:57:27 + schrieb Joakim : No, I explicitly said not the web in a subsequent post. The ignorance here of what 2G speeds are like is mind-boggling. I've used 56k and had a phone

Re: The Case Against Autodecode

On 06/01/2016 10:29 AM, Andrei Alexandrescu wrote: On 06/01/2016 06:25 AM, Marc Schütz wrote: On Tuesday, 31 May 2016 at 21:01:17 UTC, Andrei Alexandrescu wrote: The point is to operate on representation-independent entities (Unicode code points) instead of low-level representation-specific

[Issue 9114] Can't call varadic template function with partly specified template parameters

https://issues.dlang.org/show_bug.cgi?id=9114 Andrej Mitrovic changed: What|Removed |Added CC|

Re: [OT] The Case Against... Unicode?

On Wednesday, 1 June 2016 at 16:15:15 UTC, Patrick Schluter wrote: What Joakim does not understand, is that there are huge, huge quantities of documents that are multi-lingual. That should be obvious to anyone living outside the USA.

Re: Calling C++ code with pointer** argument

On Wednesday, 1 June 2016 at 07:29:56 UTC, abad wrote: That does work, though I have to explicitly cast it in my caller as well. Like this: doesNotLink(cast(const(char)**)baz2); It's a bit troublesome as my code will include quite a lot of calls like this. Casting is not necessary with the

Re: [OT] The Case Against... Unicode?

On Wednesday, 1 June 2016 at 15:02:33 UTC, Wyatt wrote: On Wednesday, 1 June 2016 at 13:57:27 UTC, Joakim wrote: No, I explicitly said not the web in a subsequent post. The ignorance here of what 2G speeds are like is mind-boggling. It's not hard. I think a lot of us remember when a 14.4

Re: D Embedded Database v0.1 Released

On Wednesday, 1 June 2016 at 16:03:09 UTC, Piotrek wrote: On Wednesday, 1 June 2016 at 09:41:43 UTC, Stefan Koch wrote: Providing a nice query interface and so on. Do you mean any form of DSL (as it's SQL for SQLite)? I hope to get by without a DSL. And instead to something nice with UFCS.

Re: mago-mi: GDB/MI compatible frontend for Mago debugger

On Wednesday, 1 June 2016 at 15:20:15 UTC, Bruno Medeiros wrote: Impressive work! I'm currently working on improving integration in VS. For this, I also needed a static library version of MagoNatDE. I just pushed my changes, I hope it doesn't break anything for you. If you want to stay in

Regex replace followed by number.

So I have ran into an issue where I want to replace a string with regex. but i cant figure out how to replace items followed by a number. i use "$1001" to do paste first match but this thinks I'm trying using match 1001 but if i try ${1}001 it gives me an error saying that it cant match the

Re: D Embedded Database v0.1 Released

On Wednesday, 1 June 2016 at 09:41:43 UTC, Stefan Koch wrote: Providing a nice query interface and so on. Do you mean any form of DSL (as it's SQL for SQLite)? Well I can see the non-realtime property being a factor for every database. And this is actually disadvantage of those databases

Re: Code security: "auto" / Reason for errors

On Wednesday, 1 June 2016 at 14:52:29 UTC, John Nixon wrote: Clearly from your comments, we have lost the argument as far as D is concerned. This leads me to question whether a computer language that is similar to D except that all variables of any type are considered in the same way as

Re: Code security: "auto" / Reason for errors

On Wednesday, 2 March 2016 at 19:42:02 UTC, Ozan wrote: Hi I despair of "auto var1 = var2"for arrays. Isn't it a open door for errors. Example import std.stdio; void main() { int[] a; foreach(i; 0..10) a ~= i; auto b = a; // correct dlang coding: auto b = a.dup;

Re: D Embedded Database v0.1 Released

On Wednesday, 1 June 2016 at 06:47:36 UTC, Suliman wrote: I still think that gitlab is bad place for DB. People prefer look sources at git or in Google. So DB should have site or git mirror to be popular. I don't think I fully understand what you mean. This is a D library not a separate

Re: Dealing with Autodecode

On 06/01/2016 11:24 AM, Jonathan M Davis via Digitalmars-d wrote: It seems more like RCString is an optimization for certain types of programs than what you'd want to use by default. You'll always want to use it. The small string optimization will make it compelling for all applications. --

Re: D Embedded Database v0.1 Released

On Tuesday, 31 May 2016 at 20:31:26 UTC, Dmitri wrote: This might provide useful information if you're aiming for something like sqlite (hopefully not offtopic): https://github.com/cznic/ql It's an embeddable database engine in Go with goals similar to yours and at an advanced stage. The

[Issue 16080] [REG2.071.0] Internal error: backend\cgobj.c 3406 when building static library

https://issues.dlang.org/show_bug.cgi?id=16080 --- Comment #4 from github-bugzi...@puremagic.com --- Commit pushed to stable at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/82c3dfb0e58f52e98ef131f9c4bb1c3c00e22939 Merge pull request #5828 from WalterBright/fix16080 fix Issue

Re: Dealing with Autodecode

On Wednesday, June 01, 2016 08:14:06 Andrei Alexandrescu via Digitalmars-d wrote: > 4. Rally behind RCStr as the preferred string type of the D language. > RCStr manages its own memory, is fast, and has the right interface (i.e. > offers several views for iteration without an implicit one,

Re: Dealing with Autodecode

On Wednesday, 1 June 2016 at 01:36:43 UTC, Adam D. Ruppe wrote: version(string_migration) deprecated void popFront(T)(ref T t) if(isSomeString!T) { static assert(0, "this is crap, fix your code."); } else deprecated("use -versionstring_migration to fix your buggy code, would you like to know

Re: Dealing with Autodecode

On Wednesday, 1 June 2016 at 02:28:04 UTC, Jonathan M Davis wrote: The other critical thing is to make sure that Phobos in general works with byDChar, byCodeUnit, etc. For instance, pretty much as soon as I started trying to use byCodeUnit instead of naked strings, I ran into this:

Re: mago-mi: GDB/MI compatible frontend for Mago debugger

On 24/05/2016 07:34, Rainer Schuetze wrote: On 17.05.2016 10:06, Vadim Lopatin wrote: Hello, I'm working on GDB/MI compatible interface for Mago debugger on Windows. GDB/MI is line based machine interface for debugger. IDEs are using GDB via this interface. GDB/MI docs:

[OT] The Case Against... Unicode?

On Wednesday, 1 June 2016 at 13:57:27 UTC, Joakim wrote: No, I explicitly said not the web in a subsequent post. The ignorance here of what 2G speeds are like is mind-boggling. It's not hard. I think a lot of us remember when a 14.4 modem was cutting-edge. Codepages and incompatible

[OT] Effect of UTF-8 on 2G connections

Am Wed, 01 Jun 2016 13:57:27 + schrieb Joakim : > No, I explicitly said not the web in a subsequent post. The > ignorance here of what 2G speeds are like is mind-boggling. I've used 56k and had a phone conversation with my sister while she was downloading a 800 MiB

Re: Code security: "auto" / Reason for errors

On Wednesday, 2 March 2016 at 21:37:56 UTC, Steven Schveighoffer wrote: Pointer copying is inherent in D. Everything is done at the "head", deep copies are never implicit. This is a C-like language, so one must expect this kind of behavior and plan for it. I sympathise with Ozan. What is

Re: PowerNex - New release of my D kernel

There is a Q about the development of the kernel over at https://www.reddit.com/r/programming/comments/4lwtn9/first_release_of_powernex_an_os_kernel_written_in/

Re: faster splitter

On Wednesday, 1 June 2016 at 13:47:10 UTC, Patrick Schluter wrote: What I wanted to say, is that in real life, the input of the search routine is very often run-time user provided data. Think of search box in browsers and apps, command line parameter à la grep, etc. The "string" search

Re: DDT 1.0.0 released.

On 17/05/2016 15:04, Bruno Medeiros wrote: New DDT release out: dfmt support, performance improvements to semantic operations, more build command customization, fixes. Please see changelog for full list: https://github.com/DDT-IDE/DDT/releases/tag/v1.0.0 Since DDT has generally been quite

Re: The Case Against Autodecode

On 06/01/2016 06:25 AM, Marc Schütz wrote: On Tuesday, 31 May 2016 at 21:01:17 UTC, Andrei Alexandrescu wrote: On 05/31/2016 04:01 PM, Jonathan M Davis via Digitalmars-d wrote: Wasn't the whole point of operating at the code point level by default to make it so that code would be operating on

Re: Dealing with Autodecode

On Wednesday, 1 June 2016 at 02:36:15 UTC, Walter Bright wrote: On 5/31/2016 6:36 PM, Adam D. Ruppe wrote: Our preliminary investigation found about 130 places in Phobos that need to be changed. That's not hard to fix! PRs please! https://github.com/dlang/phobos/pull/4322

Re: Transient ranges

On Tuesday, 31 May 2016 at 12:42:23 UTC, Steven Schveighoffer wrote: There are 2 main issues with FILE *: 1) it does not provide buffer access, so you must rely on things like getline if they exist. But these have their own problems (i.e. do not support unicode, require C-malloc'd buffer)

Re: The Case Against Autodecode

On Wednesday, 1 June 2016 at 10:04:42 UTC, Marc Schütz wrote: On Tuesday, 31 May 2016 at 16:29:33 UTC, Joakim wrote: UTF-8 is an antiquated hack that needs to be eradicated. It forces all other languages than English to be twice as long, for no good reason, have fun with that when you're

Re: faster splitter

On Wednesday, 1 June 2016 at 12:41:19 UTC, Seb wrote: On Wednesday, 1 June 2016 at 12:14:07 UTC, Patrick Schluter wrote: On Tuesday, 31 May 2016 at 17:54:34 UTC, qznc wrote: There is a special version of find for searching a single char in a string. Using a one-letter needle string is more

Re: faster splitter

On 06/01/2016 08:41 AM, Seb wrote: On Wednesday, 1 June 2016 at 12:14:07 UTC, Patrick Schluter wrote: On Tuesday, 31 May 2016 at 17:54:34 UTC, qznc wrote: There is a special version of find for searching a single char in a string. Using a one-letter needle string is more like a user mistake

Re: Dealing with Autodecode

On Wednesday, 1 June 2016 at 12:14:06 UTC, Andrei Alexandrescu wrote: On 05/31/2016 08:46 PM, Walter Bright wrote: (Shouldn't those be by!dchar, by!wchar, by!char? byCodeUnit and byCodePoint stay as they are.) 4. Rally behind RCStr as the preferred string type of the D language. RCStr

Re: faster splitter

On Wednesday, 1 June 2016 at 12:41:19 UTC, Seb wrote: On Wednesday, 1 June 2016 at 12:14:07 UTC, Patrick Schluter wrote: On Tuesday, 31 May 2016 at 17:54:34 UTC, qznc wrote: There is a special version of find for searching a single char in a string. Using a one-letter needle string is more

Re: C++ to D converter based on clang

On 1/06/2016 9:40 PM, Jacob Carlborg wrote: Yes I could. Like I could participate to VisualD/cpp2d or magicport2 projects. Anything that is not using a real front end is a lost cause. Haha that really depends on your goals.

Re: Transient ranges

On Tuesday, 31 May 2016 at 18:31:05 UTC, Steven Schveighoffer wrote: On 5/31/16 11:45 AM, Jonathan M Davis via Digitalmars-d wrote: On Monday, May 30, 2016 09:57:29 H. S. Teoh via Digitalmars-d wrote: I'd argue that range-based generic code that assumes non-transience is inherently buggy,

[Issue 16080] [REG2.071.0] Internal error: backend\cgobj.c 3406 when building static library

https://issues.dlang.org/show_bug.cgi?id=16080 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED

Re: faster splitter

On Wednesday, 1 June 2016 at 12:14:07 UTC, Patrick Schluter wrote: On Tuesday, 31 May 2016 at 17:54:34 UTC, qznc wrote: There is a special version of find for searching a single char in a string. Using a one-letter needle string is more like a user mistake than something to optimize for. At

[Issue 16080] [REG2.071.0] Internal error: backend\cgobj.c 3406 when building static library

https://issues.dlang.org/show_bug.cgi?id=16080 --- Comment #3 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/4d867e5f41bed2593d75043a09d7b5f9b432e2db fix Issue 16080 - [REG2.071.0] Internal error:

Re: Preferred method of creating objects, structs, and arrays with deterministic memory management

On Wednesday, 1 June 2016 at 08:53:01 UTC, Rene Zwanenburg wrote: I was wondering: what's the preferred method for deterministic memory management? You can annotate your functions as @nogc. The compiler will disallow any potential GC use, including calling other functions that are not

Re: faster splitter

On Tuesday, 31 May 2016 at 17:54:34 UTC, qznc wrote: There is a special version of find for searching a single char in a string. Using a one-letter needle string is more like a user mistake than something to optimize for. At compile time you may not know the length of the needle, like in the

  1   2   >