Re: std.data.json formal review

2015-08-15 Thread Dmitry Olshansky via Digitalmars-d
On 16-Aug-2015 03:50, Walter Bright wrote: On 8/15/2015 3:18 AM, Sönke Ludwig wrote: There is no reason to validate UTF-8 input. The only place where non-ASCII code units can even legally appear is inside strings, and there they can just be copied verbatim while looking for the end of the string

Re: Visual Studio Code

2015-08-15 Thread Joakim via Digitalmars-d
On Saturday, 15 August 2015 at 18:04:20 UTC, bitwise wrote: Just a side note, looking at the main page of dlang.org, I don't see any reference to who's using/contributing to D, or a link thereto. I think it would help a lot of the logos of the D language's top sponsors could be seen somewher

Re: Passing parameters to thread functions

2015-08-15 Thread D_Starter via Digitalmars-d
On Saturday, 15 August 2015 at 22:21:34 UTC, Ali Çehreli wrote: On 08/15/2015 05:22 AM, D_Starter wrote: > I haven't found anything useful on the library description so > far. In addition to the posted documentation links, I have the following chapters that may be helpful. - Message Passing

Re: std.data.json formal review

2015-08-15 Thread Jay Norwood via Digitalmars-d
On Thursday, 13 August 2015 at 10:51:47 UTC, Sönke Ludwig wrote: I think we really need to have an informal pre-vote about the BigInt and DOM efficiency vs. functionality issues. Basically there are three options for each: 1. Keep them: May have an impact on compile time for big DOMs (run tim

Re: std.data.json formal review

2015-08-15 Thread Walter Bright via Digitalmars-d
On 8/15/2015 3:18 AM, Sönke Ludwig wrote: I don't know what 'isStringInputRange' is. Whatever it is, it should be a 'range of char'. I'll rename it to isCharInputRange. We don't have something like that in Phobos, right? That's right, there isn't one. But I use: if (isInputRange!R && is(

Re: Passing parameters to thread functions

2015-08-15 Thread deadalnix via Digitalmars-d
On Saturday, 15 August 2015 at 13:20:06 UTC, Marc Schütz wrote: On Saturday, 15 August 2015 at 12:46:22 UTC, Adam D. Ruppe wrote: core.thread lets you share stuff implicitly (which can get weird with two threads writing to it at the same time). std.concurrency requires you to be more explicit a

Re: Passing parameters to thread functions

2015-08-15 Thread Ali Çehreli via Digitalmars-d
On 08/15/2015 05:22 AM, D_Starter wrote: > I haven't found anything useful on the library description so > far. In addition to the posted documentation links, I have the following chapters that may be helpful. - Message Passing Concurrency http://ddili.org/ders/d.en/concurrency.html - Dat

Re: TCP Socket Client Example

2015-08-15 Thread Laeeth Isharc via Digitalmars-d
On Friday, 14 August 2015 at 14:06:03 UTC, Kingsley wrote: Hi Does anyone have some examples of making a client socket connection to a host on a port and parsing the incoming data in some kind of loop. --K Nanomsg might be one option if you control the host - by one of the main authors of

Re: std.data.json formal review

2015-08-15 Thread Laeeth Isharc via Digitalmars-d
On Saturday, 15 August 2015 at 17:07:36 UTC, Suliman wrote: I talked with few people and they said that they are prefer current vibed's json implementation. What's wrong with it? Why do not stay old? They look more easier that new... IMHO API of current is much harder. New stream parser is f

Re: Where are the semantics of shared defined?

2015-08-15 Thread Timon Gehr via Digitalmars-d
On 08/15/2015 07:06 PM, rsw0x wrote: On Saturday, 15 August 2015 at 09:30:48 UTC, Jonathan M Davis wrote: On the whole, if you understand how a variable in C/C++/C#/Java works, you understand how shared works. It's just that unlike C++, normal variables in D are thread-local, and shared is prot

Re: Mid level IR

2015-08-15 Thread deadalnix via Digitalmars-d
On Friday, 14 August 2015 at 16:13:07 UTC, Ola Fosheim Grøstad wrote: Rust is getting a mid level IR for speeding up compilation. http://blog.rust-lang.org/2015/08/14/Next-year.html https://github.com/rust-lang/rfcs/pull/1211 It has been mentioned that before that this would be worthwhile for

Re: Nested public imports - bug or feature?

2015-08-15 Thread Timon Gehr via Digitalmars-d
On 08/15/2015 06:15 PM, Dicebot wrote: On Friday, 14 August 2015 at 20:12:43 UTC, Timon Gehr wrote: On 08/14/2015 08:57 PM, Dicebot wrote: Ok, let's stop for a minute and make sure we are on the same thread here. Because you seem to argue something I have never said or at least intended to say.

Re: Matrix API support - start with formats?

2015-08-15 Thread Daniel Shapero via Digitalmars-d
On Friday, 14 August 2015 at 14:57:19 UTC, Andrei Alexandrescu wrote: No doubt other popular linear algebra libraries have similar documentation. I was thinking we could start with adding these layouts to std, along with a few simple primitives (construction, element/slice access, stride etc).

Re: Matrix API support - start with formats?

2015-08-15 Thread Shachar Shemesh via Digitalmars-d
On 14/08/15 17:57, Andrei Alexandrescu wrote: I stumbled upon https://software.intel.com/en-us/node/471374 which gives good detail on Intel's Math Kernel Library's data formats for sparse matrices. No doubt other popular linear algebra libraries have similar documentation. I was thinking we coul

Re: Visual Studio Code

2015-08-15 Thread bitwise via Digitalmars-d
On Saturday, 8 August 2015 at 15:02:45 UTC, Andrei Alexandrescu wrote: On 8/7/15 4:07 PM, bitwise wrote: On Monday, 3 August 2015 at 00:24:56 UTC, bitwise wrote: Just stumbled upon this: https://code.visualstudio.com/ I see support for Rust and Go, but no D. If you download it, there is a li

Re: std.data.json formal review

2015-08-15 Thread Suliman via Digitalmars-d
I talked with few people and they said that they are prefer current vibed's json implementation. What's wrong with it? Why do not stay old? They look more easier that new... IMHO API of current is much harder.

Re: Where are the semantics of shared defined?

2015-08-15 Thread rsw0x via Digitalmars-d
On Saturday, 15 August 2015 at 09:30:48 UTC, Jonathan M Davis wrote: On the whole, if you understand how a variable in C/C++/C#/Java works, you understand how shared works. It's just that unlike C++, normal variables in D are thread-local, and shared is protected against interacting with them

Re: Nested public imports - bug or feature?

2015-08-15 Thread Dicebot via Digitalmars-d
On Friday, 14 August 2015 at 20:12:43 UTC, Timon Gehr wrote: On 08/14/2015 08:57 PM, Dicebot wrote: Ok, let's stop for a minute and make sure we are on the same thread here. Because you seem to argue something I have never said or at least intended to say. ... OK. This is my view: The sub-th

Re: Bug in std.container: SList

2015-08-15 Thread anonymous via Digitalmars-d
On Friday, 14 August 2015 at 19:44:17 UTC, Xinok wrote: On Friday, 14 August 2015 at 18:12:42 UTC, anonymous wrote: Other insert* functions call the private function SList.initialize() which does the null-check for _root. I am working on a PR adding the missing call in insertAfter - that's a

Re: Passing parameters to thread functions

2015-08-15 Thread D_Starter via Digitalmars-d
On Saturday, 15 August 2015 at 12:49:47 UTC, anonymous wrote: You can pass a delegate that calls the function: uint val = 7; auto thread1 = new Thread({thread_proc(val);}).start(); For the sake of simplicity this is perfectly fine and works. Data races seem possible but can be avoid

Re: Passing parameters to thread functions

2015-08-15 Thread via Digitalmars-d
On Saturday, 15 August 2015 at 12:46:22 UTC, Adam D. Ruppe wrote: core.thread lets you share stuff implicitly (which can get weird with two threads writing to it at the same time). std.concurrency requires you to be more explicit about it. Do you know whether that's intentional? The entire pag

Re: Passing parameters to thread functions

2015-08-15 Thread D_Starter via Digitalmars-d
@Adam and anonymous: This looks promising. I'll give it a try :thumbsup:

Re: Passing parameters to thread functions

2015-08-15 Thread anonymous via Digitalmars-d
On Saturday, 15 August 2015 at 12:22:08 UTC, D_Starter wrote: int main() { uint var = 7; auto thread1 = new Thread(&thread_proc, val).start(); /* similar to C++ STL */ thread1.join(); return 0; } [/CODE] You might have guessed...this won't work. So how do I pass parameters t

Re: Passing parameters to thread functions

2015-08-15 Thread Adam D. Ruppe via Digitalmars-d
In the documentation, it talks about derived threads in one of the examples. That's one way to do this: import core.thread; // Thread sub class can hold data // we pass the params through the constructor class MyThread : Thread { uint* var; // ref only works one level deep - it s

Re: Passing parameters to thread functions

2015-08-15 Thread D_Starter via Digitalmars-d
On Saturday, 15 August 2015 at 12:22:08 UTC, D_Starter wrote: Hey there, I'm in the process of learning D, switching from C/C++ and Pascal. In this I've come across multithreading capabilities. What I'm trying to achieve is to create a thread, call a thread function with parameters and have

Passing parameters to thread functions

2015-08-15 Thread D_Starter via Digitalmars-d
Hey there, I'm in the process of learning D, switching from C/C++ and Pascal. In this I've come across multithreading capabilities. What I'm trying to achieve is to create a thread, call a thread function with parameters and have the thread return something. Like this: [CODE] import core.t

Re: std.data.json formal review

2015-08-15 Thread Sönke Ludwig via Digitalmars-d
Am 14.08.2015 um 10:17 schrieb Walter Bright: On 8/13/2015 11:52 PM, Sönke Ludwig wrote: Am 14.08.2015 um 02:26 schrieb Walter Bright: On 8/13/2015 3:51 AM, Sönke Ludwig wrote: These were, AFAICS, the only major open issues (a decision for an opt() variant would be nice, but fortunately that's

Truly lazy ranges, transient .front, and std.range.Generator

2015-08-15 Thread Joseph Rushton Wakeling via Digitalmars-d
Hello all, One of the design considerations I've been mulling over recently, in terms of random number generation functionality, is that while we talk of ranges being lazily evaluated, in fact this isn't strictly true. Most ranges are in fact a mix of lazy and eager: lazy in their use of popF

Re: Where are the semantics of shared defined?

2015-08-15 Thread Jonathan M Davis via Digitalmars-d
On Friday, 14 August 2015 at 18:52:42 UTC, rsw0x wrote: On Friday, 14 August 2015 at 12:43:26 UTC, thedeemon wrote: Anrei's TDPL book spent a lot of words on shared (and this book had kind-of-a-spec reputation), but I don't know how much of it is relevant now. I know for a fact that a lot of

Re: std.data.json formal review

2015-08-15 Thread via Digitalmars-d
On Saturday, 15 August 2015 at 05:03:52 UTC, Walter Bright wrote: On 8/14/2015 9:58 PM, suliman wrote: On Friday, 14 August 2015 at 20:44:59 UTC, Walter Bright wrote: Config files will work fine with json format. Walter, and what I should to do for commenting stringin config for test purpose?