from:"Etienne"


On Sunday, 28 June 2015 at 15:09:25 UTC, Suliman wrote:

On Saturday, 27 September 2014 at 18:21:18 UTC, Etienne wrote:

On 2014-09-27 2:13 PM, Etienne wrote:

engine (I have an ASN1 library in the works as well).


It's nearly finished, it will allow BER/DER serialization to 
take place from UDAs and native types at compile-time:


https://github.com/globecsys/asn1.d


/// Usage: run() the object, start watching directories, 
receive an event in your handler,

/// read the changes by draining the buffer.

Could you show how to use it for monitoring FS?

I did
import libasync.watcher;

So now I need simply call run()? But how to pass folder path to 
it?



void main()
{
bool run()
{
return 0;
}

}


It's seems that I missing something...


You can see an example in libasync.tests

Re: Announcing libasync, a cross-platform D event loop


On Sunday, 28 June 2015 at 16:32:24 UTC, Suliman wrote:

You can see an example in libasync.tests


thanks! I have got few questions
g_cbCheck = new shared bool[19];
what does it do?

AsyncDirectoryWatcher g_watcher = new 
AsyncDirectoryWatcher(getThreadEventLoop());
Am I right understand that it's run new eventloop inside 
AsyncDirectoryWatcher function?


The g_cbCheck is specific to this unit test, everytime a callback 
succeeds it will set its index to true in the array.


The event loop must be passed to the async object because the 
watcher will register itself to it when it is run.


When you've registered your callback in the watcher and run it 
through the event loop, you have to run the event loop and events 
will be pushed to your callback

Re: Announcing libasync, a cross-platform D event loop

2015-06-30 Thread Etienne Cimon via Digitalmars-d


On Sunday, 28 June 2015 at 16:57:44 UTC, Suliman wrote:
Also next code that I take from example after run absolutely do 
not do nothing:


This code will register a directory watcher in the working 
directory, on the thread's event loop, and then use timers to 
create file/folder activity to trigger this directory watcher.


The only thing needed to make this work is r/w access to the 
working directory and a running event loop.


So, adding the line:

g_evl.run(10.seconds);

If you don't have an event loop running, your application is 
basically not going to receive callback events.

Re: Announcing libasync, a cross-platform D event loop

2015-06-30 Thread Etienne Cimon via Digitalmars-d


On Sunday, 28 June 2015 at 17:10:16 UTC, Etienne Cimon wrote:

g_evl.run(10.seconds);


Hmm, sorry that would be g_evl.loop(10.seconds) or 
getThreadEventLoop().loop(10.seconds). I use the vibe.d driver 
most often.

Re: Heisenbug involving Destructors GC - Help Needed

On Tuesday, 30 June 2015 at 17:10:41 UTC, Steven Schveighoffer 
wrote:

On 6/30/15 10:04 AM, Etienne wrote:

I don't think there's a problem with destroy in the first 
place. The
problem is that it's being advertised as calling the 
destructors:


It does for value types and for class references.

-Steve


Yeah well the types that don't get finalized by it need to be 
listed somewhere

Re: Announcing libasync, a cross-platform D event loop


On Tuesday, 30 June 2015 at 04:38:31 UTC, suliman wrote:
Ok, but code still do exit after it's run. Look like loop is 
not started


Yes, you need to watch for the return type which will be false in 
case of error


while(getThreadEventLoop().loop(10.seconds))
continue;

writeln(getThreadEventLoop().error);

Re: Heisenbug involving Destructors GC - Help Needed


On Tuesday, 30 June 2015 at 14:04:45 UTC, Etienne wrote:
On Tuesday, 30 June 2015 at 13:01:46 UTC, Steven Schveighoffer 
wrote:

[...]


I don't think there's a problem with destroy in the first 
place. The problem is that it's being advertised as calling the 
destructors:


http://dlang.org/library/object/type_info.destroy.html
http://dlang.org/library/object/destroy.html

The function would need a documentation section itself, since 
it's being advertised as a replacement for `delete` and 
expected to do the same wherever there's something to read 
about it.


We probably just need a new page in the `D Reference` about 
Lifetime. Documenting the general behavior and good practices of 
anything that manages lifetime, e.g. malloc, free, delete, 
destroy, new, pointers, classes, base types, etc.

Re: Heisenbug involving Destructors GC - Help Needed

On Tuesday, 30 June 2015 at 13:01:46 UTC, Steven Schveighoffer 
wrote:

On 6/26/15 11:38 PM, Brian Schott wrote:

On Saturday, 27 June 2015 at 03:16:35 UTC, rsw0x wrote:
calling destroy on a pointer should either be fixed or be an 
error,

that should not be allowed to happen.


Completely agreed. Calling destroy() on a pointer has been 
incorrect

EVERY time I've seen it done.


I'd say if you want to see cases where it was done correctly, 
change the behavior and watch the complaints come in ;)


Wouldn't destroying the pointer target make an assumption about 
ownership?


Consider a struct that contains a pointer:

struct S
{
   T *x;
}

destroy's algorithm for this struct is to call destroy on all 
of the members, then set to S.init. But what if S is just 
*referencing* that T, and doesn't *own* it? Isn't this the 
wrong thing to do?


I agree it's inconsistent with class references. How to make it 
consistent isn't as easy to decide. For me, it's the class 
destruction which is incorrect. Consider that destroy is 
consistent with scope destruction for every type except for 
classes:


class C {}
struct S {}

{
   C c = new C;
   S s;
   S *s2 = new S;
} // calls s.dtor, does not call c.dtor or s2.dtor

And what about arrays? Should calling destroy on an array call 
destroy on all of the elements (it currently doesn't)?


If I were to design destroy from scratch, I'd make destroy, and 
destroyRef (which destroys referenced data via pointer or 
class).


-Steve


I don't think there's a problem with destroy in the first place. 
The problem is that it's being advertised as calling the 
destructors:


http://dlang.org/library/object/type_info.destroy.html
http://dlang.org/library/object/destroy.html

The function would need a documentation section itself, since 
it's being advertised as a replacement for `delete` and expected 
to do the same wherever there's something to read about it.

Re: Announcing libasync, a cross-platform D event loop

2015-06-30 Thread Etienne Cimon via Digitalmars-d


On Sunday, 28 June 2015 at 19:34:46 UTC, Suliman wrote:

void main()
{

void dirWatcher()
{
		auto g_watcher = new 
AsyncDirectoryWatcher(getThreadEventLoop());

g_watcher.run({
DWChangeInfo[1] change;
DWChangeInfo[] changeRef = change.ptr[0..1];
while(g_watcher.readChanges(changeRef)){
writeln(change);
}
});
g_watcher.watchDir(.);
getThreadEventLoop();

}

dirWatcher();

//destroyAsyncThreads();

}
Is this code enough to monitoring folder?

If I run it it's terminating, it's seems that eventloop not 
starting or I placed it in wrong place?


You should do getThreadEventLoop().loop(); and it will monitor 
the changes forever. Try making changes in the filesystem 
manually :)

Re: Announcing libasync, a cross-platform D event loop

2015-06-30 Thread Etienne Cimon via Digitalmars-d


On Sunday, 28 June 2015 at 18:33:28 UTC, Suliman wrote:
Hmm, sorry that would be g_evl.loop(10.seconds) or 
getThreadEventLoop().loop(10.seconds). I use the vibe.d driver 
most often.


I changed paths to hardcoded to prevent issue with them, but 
next code after run only create hey folder and nothing more. 
No files in it:


Try putting the timers outside the callbacks in the meantime. 
I'll test it tomorrow when I'm at the office =)




--
And how to detect if some there was some manipulation inside 
monitoring folder? How I can recive name of file that was added 
to folder?


There's a path in the DWFileChange change structure, you can 
access it with change.path. You'll have to put it in a path 
parser to access the filename, such as std.path

Re: Announcing libasync, a cross-platform D event loop


On Monday, 29 June 2015 at 20:34:11 UTC, Suliman wrote:
Ehm, there is issue on Windows or I am again doing something 
wrong?


void main()
{

void dirWatcher()
{
 		auto g_watcher = new 
AsyncDirectoryWatcher(getThreadEventLoop());

g_watcher.run({
DWChangeInfo[1] change;
DWChangeInfo[] changeRef = change.ptr[0..1];
while(g_watcher.readChanges(changeRef)){
writeln(change);
}
});
g_watcher.watchDir(.);
getThreadEventLoop().loop();
}

 dirWatcher();

 destroyAsyncThreads();

}


Without destroyAsyncThreads(); it's fail with exception.


Yes that line is required

Re: Question about Walter's Memory DisAllocation pattern

2015-06-27 Thread Etienne Cimon via Digitalmars-d


On 2015-06-27 01:06, thedeemon wrote:

On Saturday, 27 June 2015 at 03:10:51 UTC, Etienne Cimon wrote:


What you're asking for is probably type inference. Notice the auto
return type? This keyword is actually very advanced and bleeding edge
in natively compiled languages.


Inference of return type was in ML since 1973. Such bleeding, so edge. ;)


Is there some other natively compiled language that implemented the auto 
keyword before? Or are you only talking about the theory?

Re: Heisenbug involving Destructors GC - Help Needed

2015-06-27 Thread Etienne via Digitalmars-d


On Saturday, 27 June 2015 at 12:28:26 UTC, Kagamin wrote:
On Friday, 26 June 2015 at 18:27:34 UTC, Maxime 
Chevalier-Boisvert wrote:
I seem to have run into a heisenbug involving destructors and 
the GC. I'm kind of stuck at this point and need help tracking 
down the issue.


BTW, how GC performance is doing? Etienne is experimenting with 
thread local GC: 
http://forum.dlang.org/post/nfuzudyoatryapcwx...@forum.dlang.org which also proved to be faster. But only if single-threaded GC is good enough for you, which normally should be given single-threaded model of javascript.


The new keyword can leverage the shared keyword to place certain 
objects in a shared GC, which can coexist with the local GC 
without fundamental changes. ie std.concurrency already requires 
that you pass shared objects, but casting won't cut it anymore 
you'll actually have to duplicate the object on the shared GC 
with .sdup or create it there with new shared. I don't need a 
shared GC right now so I'm not pushing too much for it, I'm 
satisfied with keeping a pointer of the object alive in the 
thread it was created and that's all a thread local GC really 
requires for concurrency to work

Re: Heisenbug involving Destructors GC - Help Needed

2015-06-26 Thread Etienne Cimon via Digitalmars-d

On 2015-06-26 14:27, Maxime Chevalier-Boisvert wrote:

I seem to have run into a heisenbug involving destructors and the GC.
I'm kind of stuck at this point and need help tracking down the issue.

I put the broken code in a branch called heisenbug on github:
https://github.com/higgsjs/Higgs/tree/heisenbug

The problem manifests itself on runs of `make test` (my unittests), but
only some of the time. I wrote a script to run `make test` repeatedly to
try and find a solution:
https://github.com/higgsjs/Higgs/blob/heisenbug/source/repeatmaketest.py

The problem usually manifests itself after 5 to 15 runs on my machine. I
get a segmentation fault, not always in the same place. The randomness
seems to stem from address space randomization.

It seems the issue is caused by my freeing/reinitializing the VM during
unit tests. More specifically, commenting out this line makes the
problem go away:
https://github.com/higgsjs/Higgs/blob/heisenbug/source/runtime/vm.d#L741

Higgs can run all of my benchmarks without ever failing, but restarting
the VM during `make test` seems to be causing this problem to happen.
It's not impossible that there could be another underlying issue, such
as the JITted code I generate corrupting some memory location, but it
would seem that if this were the case, the issue would likely show up
outside of unit tests. Any help would be appreciated.

This might come as a surprise to you as much as it did to me at the
time, but when you have GCRoot* root; where GCRoot is a struct, if you
destroy(root), you're setting your local pointer to null. You're not
actually calling the destructor on the struct.

Also, I would avoid throwing of any type in a destructor.

https://github.com/higgsjs/Higgs/blob/0b48477120c4acce46a01b05a1d4b035aa432550/source/jit/codeblock.d#L157

Re: Question about Walter's Memory DisAllocation pattern

2015-06-26 Thread Etienne Cimon via Digitalmars-d


On 2015-06-26 22:45, Parke via Digitalmars-d wrote:

Hi,

I have a question about Walter's DConf keynote and the Memory
DisAllocation pattern.

http://dconf.org/2015/talks/bright.html

The following example is from the slides of Walter's talk.



auto toString(uint u) {
   static struct Result {
 this(uint u) {
   idx = buf.length;
   do {
 buf[--idx] = (u % 10) + '0';
 u /= 10;
   } while (u);
 }
 @property bool empty() { return idx == buf.length; }
 @property char front() { return buf[idx]; }
 void popFront() { ++idx; }
 char[uint.sizeof * 3] buf;
 size_t idx;
   }
   return Result(u);
}

import std.stdio;

void main() { writeln(toString(28)); }



My question is:

Does use of this pattern in D require that the size of the Result
struct be known by the compiler at compile time?

Or, perhaps more precisely:  Does the caller of toString need to know
the size of the struct that toString will return?

In the above example, buf's length is uint.sizeof * 3.  But what if
buf's length was a function of u (and therefore only known at
run-time), rather than a function of uint.sizeof?

Thanks!

-Parke



What you're asking for is probably type inference. Notice the auto 
return type? This keyword is actually very advanced and bleeding edge in 
natively compiled languages.


Internally, when the function is processed by the compiler, all types 
are evaluated before the instructions are even looked at, and the final 
size of all types are compiled and automatically put in place.


Afterwards, the instructions must obey consistency, ie. the caller can't 
use anything but auto or ReturnType!toString to accept an auto type 
because there's no way you can guess the mangling/size/etc otherwise.


This also means you can choose a ridiculous name or you can change the 
size of a stack allocated object any time without breaking an interface.


e.g. you could change this without breaking the API to something like:

auto toString(T)(T u) if (isNumeric!T) {
   static struct GenericResult {
 this(T u) {
   ...
char[T.sizeof * 3] buf;
...
}

Re: Heisenbug involving Destructors GC - Help Needed

2015-06-26 Thread Etienne Cimon via Digitalmars-d


On 2015-06-26 23:44, Temtaime wrote:

Disagree. Destroy on a pointer calls dtor of a struct.
Why it should be an error ?


Exactly what I assumed too. Can you imagine all of the random errors 
that stem from such a basic, low-level assumption? I carry a scar for 
every day I've spent in the debugger, and this bug has given me its load 
of torments. Of course, I'm the only one to blame, I didn't know:


import std.stdio;

void main() {
struct A { ~this() { writeln(Dtor); } }
A* a = new A;
destroy(a);
writeln(Done);
}

output: Done

Re: PHP verses C#.NET verses D.

2015-06-25 Thread Etienne via Digitalmars-d


On Wednesday, 24 June 2015 at 05:34:08 UTC, Nick B wrote:

On Tuesday, 23 June 2015 at 11:22:40 UTC, Etienne Cimon wrote:



Nick


I don't have current performance results because I've been 
focused on adding features, but these results were taken on a 
previous version:


https://atilanevesoncode.wordpress.com/2013/12/05/go-vs-d-vs-erlang-vs-c-in-real-life-mqtt-broker-implementation-shootout/


Etienne

Thanks for the responses and your details replies.
I'm going to talk to the CEO of the company described, at the 
beginning of this long thread, and find out they are willing to 
consider a proof of concept web site based on your work.
This could take a couple of weeks.  What is the best way to get 
in touch with you if I have more questions ?


Nick


Skype: Etcimon or gmail the same username

Re: PHP verses C#.NET verses D.

2015-06-23 Thread Etienne Cimon via Digitalmars-d


On Tuesday, 23 June 2015 at 06:26:39 UTC, Nick B wrote:

On Thursday, 18 June 2015 at 03:44:08 UTC, Etienne Cimon wrote:

So now I can build a full web application/server executable in 
less than 2mb packed, and it runs faster than anything out 
there.


Etienne

Do you have an performance numbers, as to how fast your web 
application/server is, or is this based on your personal 
experience ?


Nick


I don't have current performance results because I've been 
focused on adding features, but these results were taken on a 
previous version:


https://atilanevesoncode.wordpress.com/2013/12/05/go-vs-d-vs-erlang-vs-c-in-real-life-mqtt-broker-implementation-shootout/

Re: PHP verses C#.NET verses D.


On Monday, 22 June 2015 at 06:32:31 UTC, Nick B wrote:

On Thursday, 18 June 2015 at 03:44:08 UTC, Etienne Cimon wrote:



Etienne

Would you like to detail what still needs to be completed/on 
the to-do list  ?


What would be the best way to learn it ?

Does it need documentation as well ?

Nick


The docs should be the same as the ones on vibed.org

As for the todo list, It's a little long to detail it. Depends 
also on where you want to go.


Urgent:
- Update libhttp2 and botan with recent changes from the original 
repos (nghttp2, botan). No stability issues, only new algorithms 
mostly.
- Write a Windows/Mac/linux daemon utility with rights elevation 
to have support for desktop application development (currently 
finishing up windows)
   - The Mac daemon requires launchd, which compiles only with 
DMD pull request to be merged: 
https://github.com/D-Programming-Language/dmd/pull/4321

   - Uses the http://diveframework.com/ to elevate
- Test the live debugging features with third party applications 
(similar to packet-capturing but server-side).
   - This is completed and available on my fork of vibe.d and a 
reverse proxy request looks like this: 
http://htmlpreview.github.io/?https://github.com/etcimon/vibe.d/blob/master/views/capture.html = http://pastebin.com/raw.php?i=E51RXyt2
   - Also includes json req/response or call stack in builds 
compiled with release
- Try running with LDC and debug the libraries until everything 
completely compiles with it (2.067+)
- Find a way to add a thread-local GC in druntime or at least 
make dub compile the projects with it.


Less urgent:
- Implement administration interface for the new redis 3.0 
clustering feature

- Write a DNS server with A-record scheduling for distribution
- Adapt VibeDist to send requests to worker tasks
- Add support for runtime loading of DLL plugins that 
auto-register/unregister to the router.

- Test lua bindings to develop runtime themes

I also have private application development on the todo list 
which ends up testing the library. Lots of testing is still 
needed but I think the server exceeds what I could make any other 
server do. It compiles in a single portable executable 2mb packed 
after all.

Re: Future(s) for D.


On Monday, 22 June 2015 at 19:45:57 UTC, Jacob Carlborg wrote:

On 22/06/15 14:46, Etienne wrote:

[...]



[...]


Seems I need to actually make a try on using these libraries.


[...]


In general I feel it hard to justify when everything is already 
implemented in Ruby. At some point I just want to use a 
language and the libraries without needing to reinvent the 
wheel. Back in 2006 when I started with D I had some idea for 
an application I wanted to build. But there were a lot of 
missing components (many still are), I still haven't started 
building that application.


I can't really know how it would've been like back then. Today it 
looks like there might be a future in web dev for D, I'd think 
people are willing to invest their name on a library to be part 
of it.

Re: Future(s) for D.


On Monday, 22 June 2015 at 11:29:50 UTC, Jacob Carlborg wrote:

On 22/06/15 01:43, Nick Sabalausky wrote:


Curiosity, what libraries do you feel a lack of?


For work, that would be:

* Database drivers for Postgres and SQLite

https://github.com/etcimon/d2sqlite3
async with vibe.d : 
https://github.com/pszturmaj/ddb/blob/master/examples/basic.d#L7

* ORM

https://github.com/buggins/hibernated

* Unit test framework. I want something like RSpec

I always got around fine with unittest { } and some imagination

* RabbitMQ and ActiveMQ

C=D binding and register sockets in libasync?

* Some way to interface with Selenium and PhantomJS


You need to write the javascript to a file and use executeShell 
or pipeShell.
I wanted to write a forward proxy in vibe.d though so that we can 
actually handle the headers/cookies and analyze the contents over 
the wire. I'm not sure if there's a language that does that 
already




For non work related things it would also be:

* Sass

https://github.com/Lodin/sassed

* CoffeeScript

https://github.com/MartinNowak/diet-coffee/blob/master/source/diet_coffee.d#L23
* I would prefer HAML over that templates used in vibe.d but I 
guess there' close enough

http://blog.seancarpenter.net/2013/05/24/using-haml-from-the-command-line/

You seem to be active member of the community. Why not attempt to 
solve those? Doesn't seem like it would take that long (all the 
primitives are there).


@rikki  I really do want to fix this. Unfortunately writing 
everything from a an actual webserver to the template live 
reloading is a lot harder then you'd think. Which is unfortunate.


You should have everything you need to write a D version of 
Wordpress using its code as a reference. Maybe with vibe.d, 
putting the data in Redis and using some lua scripting for themes 
or configuration files. It would take some imagination but it's 
not at all impossible to achieve it.

Re: Future(s) for D.


On Monday, 22 June 2015 at 14:03:47 UTC, Laeeth Isharc wrote:

On Monday, 22 June 2015 at 11:29:50 UTC, Jacob Carlborg wrote:

On 22/06/15 01:43, Nick Sabalausky wrote:


Curiosity, what libraries do you feel a lack of?


For work, that would be:



* Some way to interface with Selenium and PhantomJS


It's not pretty, but for what I want to do I have found 
embedding Python calls to phantomjs code within a D program 
works quite well.


The SQLite stuff looks okay, although I haven't used for a big 
project yet.


This is how I use it as a persistent storage for property 
get/setters. Takes some imagination at first, but it saves a huge 
amount of time/headaches on the long run.


/// Opens the SQLite database from the data folder. The user must 
call .close() when finished!

Database openDB(bool read = true) {
// DB is always created in static ctor
	return Database(DATA_FOLDER_PATH() ~ my.db, read ? 
SQLITE_OPEN_READONLY : (SQLITE_OPEN_READWRITE | 
SQLITE_OPEN_CREATE));

}


private T get(T)(string name, lazy T default_value = T.init) {
Database sqlite = openDB(READ);
scope(exit) sqlite.close();
T ret;
try {
			auto results = sqlite.execute(SELECT value FROM config WHERE 
name=' ~ name ~ ';);

auto val = results.oneValue!string;
ret = val.to!T;
}
catch { ret = default_value; }
return ret;
}

private void set(T)(string name, T value) {
Database sqlite = openDB(WRITE);
scope(exit) sqlite.close();
bool exists;
try {
			ResultRange res = sqlite.prepare(SELECT value FROM config 
WHERE name=?;).bind(1, name).execute();
			string val = res.oneValue!string; // will throw if the value 
is not there

// Update the existing value.
			auto prep = sqlite.prepare(UPDATE TABLE config SET value=? 
WHERE name=?;).bind(1, name).execute();

prep.bind(1, value.to!string);
res = prep.execute();
}
catch {
exists = false;
}

if (!exists) {
			auto res = sqlite.prepare(INSERT INTO config (name, value) 
VALUES (?, ?);).bind(1, name).bind(2, value.to!string).execute();

}
}

// usage:

@property Duration created() {
return get!ulong(created, 120).dur!seconds;
}

@property void created(Duration val) {
set(created, val.total!seconds);
}

Re: PHP verses C#.NET verses D.

2015-06-21 Thread Etienne Cimon via Digitalmars-d


On Sunday, 21 June 2015 at 03:16:31 UTC, Nick B wrote:

On Friday, 19 June 2015 at 11:28:30 UTC, Etienne Cimon wrote:

On Thursday, 18 June 2015 at 05:23:25 UTC, Nick B wrote:
On Thursday, 18 June 2015 at 03:44:08 UTC, Etienne Cimon 
wrote:




Will you explain how it is different to Vibe.d ?


It has HTTP/2, a new encryption library, it uses a native TCP 
event library, lots of refactoring. In short, the entire thing 
is in D rather than linking with OpenSSL and libevent.



Etienne

Can you explain the benefits of writing these libraries in D, 
as against just linking to  these libraries. Is it for faster 
execution, or better debugging, or some other reason ?


When writing bindings, you need to write unit tests for your 
bindings and an interface. You're adding a layer of software with 
its own propensity for errors. You also don't have access to the 
underlying implementation in the IDE. You also can't add features 
to facilitate your own programs unless you control the repository.


Honestly, I can't stand having layers and layers of garbage to 
make up for language differences. I like the cleanliness of it 
all and it probably ended up taking me half the time because I 
avoided debugging new code.

Re: Future(s) for D.

2015-06-21 Thread Etienne Cimon via Digitalmars-d


On Sunday, 21 June 2015 at 19:08:47 UTC, Jacob Carlborg wrote:

On 20/06/15 16:00, Etienne wrote:

Yep, looks like we already have better. I don't understand how 
D hasn't

fully picked up in Web Dev at this point. Are they expecting an
e-commerce/blogging/cms platform to go with it?


My biggest reason is the lack of libraries.


There's probably a lack of a Joomla/Wordpress/Magento platform in 
D with plugin support. Libraries would pour into D if there was a 
similar tool.

Re: Future(s) for D.

2015-06-20 Thread Etienne via Digitalmars-d


On Saturday, 20 June 2015 at 13:33:34 UTC, Dragos Carp wrote:

On Saturday, 20 June 2015 at 12:35:11 UTC, weaselcat wrote:
I recently read this facebook post on their future 
implementation in their Folly library.


https://code.facebook.com/posts/1661982097368498

This made me slightly envious. Thoughts on a D implementation?


Even if the callbacks are sequentially listed, the callback 
hell is still there.


A better solution is to use fibers. You can take a look at a 
fibers[1] and tasks[2] implementation in asynchronous 
library[3].


[1] - 
https://github.com/dcarp/asynchronous/blob/master/src/asynchronous/futures.d
[2] - 
https://github.com/dcarp/asynchronous/blob/master/src/asynchronous/tasks.d

[3] - http://code.dlang.org/packages/asynchronous


Yep, looks like we already have better. I don't understand how D 
hasn't fully picked up in Web Dev at this point. Are they 
expecting an e-commerce/blogging/cms platform to go with it?

Re: Future(s) for D.

2015-06-20 Thread Etienne via Digitalmars-d


On Saturday, 20 June 2015 at 22:42:23 UTC, Ellery Newcomer wrote:

On 06/20/2015 07:00 AM, Etienne wrote:

On Saturday, 20 June 2015 at 13:33:34 UTC, Dragos Carp wrote:

On Saturday, 20 June 2015 at 12:35:11 UTC, weaselcat wrote:

[...]


Even if the callbacks are sequentially listed, the callback 
hell is

still there.

A better solution is to use fibers. You can take a look at a 
fibers[1]

and tasks[2] implementation in asynchronous library[3].

[1] -
https://github.com/dcarp/asynchronous/blob/master/src/asynchronous/futures.d

[2] -
https://github.com/dcarp/asynchronous/blob/master/src/asynchronous/tasks.d

[3] - http://code.dlang.org/packages/asynchronous


Yep, looks like we already have better. I don't understand how 
D hasn't

fully picked up in Web Dev at this point. Are they expecting an
e-commerce/blogging/cms platform to go with it?


A while back I was bored and curious to see how vibe would fare 
in the web framework benchmarks 
(http://www.techempower.com/benchmarks/) so I started adding 
vibe to it (https://github.com/ariovistus/FrameworkBenchmarks).


Chose to go with ddb. Postgresql+asynchronous, sounds great. It 
didn't compile with the latest dmd at the time. So I fixed it 
up, made a PR, and it worked fine.


It looked like I was getting results close to netty (in json 
serialization) without much effort, but ultimately, I set it 
aside to wait for my PR to be merged.


what is the deal with ddb, anyways? Is it dead?


Hm, ddb doesn't have an asynchronius driver so you're probably 
going through std.socket which is thread blocking. I think the 
author isn't very active, but you shouldn't make it a habit to 
wait for a merge before continuing, or else you'll never be 
productive. Worst case your fork will be more up to date and you 
can become the maintainer I guess

Re: PHP verses C#.NET verses D.

2015-06-19 Thread Etienne Cimon via Digitalmars-d


On Friday, 19 June 2015 at 11:29:58 UTC, Etienne Cimon wrote:

On Friday, 19 June 2015 at 11:28:30 UTC, Etienne Cimon wrote:

On Thursday, 18 June 2015 at 05:23:25 UTC, Nick B wrote:
On Thursday, 18 June 2015 at 03:44:08 UTC, Etienne Cimon 
wrote:

[...]




Also, the HTTP client has a cookiejar and more settings.


hmm, I think I can mention the capture debugger. I'm still 
developing it but it's becoming quite complete. It's a runtime 
tool shows the HTTP client/server request/response headers, form 
files/fields, json input/output, for specific request paths, and 
works in builds without debug info. The trace library that's used 
for it also maintains custom call stack trace that works in 
builds withoutu debug info.


https://htmlpreview.github.io/?https://github.com/etcimon/vibe.d/blob/master/views/capture.html

Re: PHP verses C#.NET verses D.

2015-06-19 Thread Etienne Cimon via Digitalmars-d


On Thursday, 18 June 2015 at 05:23:25 UTC, Nick B wrote:

On Thursday, 18 June 2015 at 03:44:08 UTC, Etienne Cimon wrote:
On Wednesday, 17 June 2015 at 18:40:01 UTC, Laeeth Isharc 
wrote:
 Any idea how far away it might be from being something that 
someone could use in an enterprise environment simply, in the 
same kind of way that vibed is easy?  I appreciate that 
making it broadly usable may not be what interests you, and 
may be a project for someone else.


I would say 3 months. So it'll probably be a year considering 
how off my last estimates were.


Etienne -
Interesting back story.

Will this be under a Boost licence ?

Will you provide a link ?



Even the vibe.d library was much more advanced than what I 
could find with an open source license that allowed static 
compilation at the time (1 yr 1/2 ago), so I went forward with 
that and worked my way through.


[snip\]


So now I can build a full web application/server executable in 
less than 2mb packed, and it runs faster than anything out 
there. It's standalone, works cross-platform, etc.


Will you explain how it is different to Vibe.d ?


It has HTTP/2, a new encryption library, it uses a native TCP 
event library, lots of refactoring. In short, the entire thing is 
in D rather than linking with OpenSSL and libevent.


It's MIT licensed. I have it here: 
https://github.com/etcimon/vibe.d


The dub.json uses relative paths though while I'm developing. 
You're free to adjust the file and try it, we can consider it 
stable.

Re: PHP verses C#.NET verses D.

2015-06-19 Thread Etienne Cimon via Digitalmars-d


On Friday, 19 June 2015 at 11:28:30 UTC, Etienne Cimon wrote:

On Thursday, 18 June 2015 at 05:23:25 UTC, Nick B wrote:

On Thursday, 18 June 2015 at 03:44:08 UTC, Etienne Cimon wrote:

[...]


Etienne -
Interesting back story.

Will this be under a Boost licence ?

Will you provide a link ?


[...]


[snip\]

[...]
It has HTTP/2, a new encryption library, it uses a native TCP 
event library, lots of refactoring. In short, the entire thing 
is in D rather than linking with OpenSSL and libevent.


Also, the HTTP client has a cookiejar and more settings.

Re: PHP verses C#.NET verses D.

2015-06-19 Thread Etienne via Digitalmars-d


On Friday, 19 June 2015 at 11:35:07 UTC, Suliman wrote:
It has HTTP/2, a new encryption library, it uses a native TCP 
event library, lots of refactoring. In short, the entire thing 
is in D rather than linking with OpenSSL and libevent.


It's MIT licensed. I have it here: 
https://github.com/etcimon/vibe.d


Cool!
1. Do you plain to merge it's with original dub?


Work is in progress, it will be gradual over the next year to 
avoid merge conflicts with existing users:

https://github.com/rejectedsoftware/vibe.d/tree/http2-botan-cleanup

Don't expect that branch to build though.

2. new encryption library does it's written entirely in D and 
do all that do OpenSSL?


Botan does everything that OpenSSL does, but also in a more 
convenient way. If you need something for anything crypto, 
chances are it's going to do it.


https://github.com/etcimon/botan

3. Do you any plan to add some futures from net.curl? I really 
dislike to use it, I would like native lib.


Vibe.d tasks are one level further from my point of view. You can 
write procedural TCP read/write and the thread will not block.

Re: PHP verses C#.NET verses D.

2015-06-19 Thread Etienne via Digitalmars-d


On Friday, 19 June 2015 at 15:31:19 UTC, Nick Sabalausky wrote:

On 06/19/2015 07:28 AM, Etienne Cimon wrote:


The dub.json uses relative paths though while I'm developing. 
You're

free to adjust the file and try it,


You may want to consider just using dub's (add|remove)-local 
for that instead. You can rip those path elements out of 
dub.json completely, then just do:


$ dub add-local ../botan
$ dub add-local ../libasync

And it will use those paths on your machine only, without 
mucking up the dub.json.


Then when you're done (or if you want to change paths):

$ dub remove-local ../botan
$ dub remove-local ../libasync


I don't know why so many people take it personal, I love being 
corrected. Thanks so much for the tip :)

Re: Workaround for typeid access violation

2015-06-18 Thread Etienne Cimon via Digitalmars-d


On Thursday, 18 June 2015 at 11:43:18 UTC, ketmar wrote:

On Wed, 17 Jun 2015 22:35:12 +, Etienne Cimon wrote:


e.g. __gshared MyObj g_obj1;

Thread 1: g_obj1 = new MyObj;
Thread 2: g_obj1.obj2 = new MyObj;
Thread 3: write(g_obj1.obj2); -- access violation (probably)


so no way to anchor the whole object tree by assigning it to 
__gshared root? sure, this will never make it into mainline.


__gshared is a little sketchy. We can have TLS GC by default by 
piping `new shared` to a shared GC. It's even safer, because then 
we have the type system helping out.


e.g. shared MyObj g_obj1;
Thread 1: g_obj1 = new shared MyObj;
Thread 2: g_obj1.obj2 = new shared MyObj;
Thread 3: write(g_obj1.obj2); -- success!

Re: Martin Nowak is officially MIA


On Thursday, 18 June 2015 at 20:58:38 UTC, ketmar wrote:

On Thu, 18 Jun 2015 14:45:26 +, Etienne wrote:

My point is, we need to be able to extend it to build and link 
an application with a custom druntime/phobos/dmd version from 
source.


exactly what you can do with Reggae. now Reggae needs a good 
package manager, which dub isn't.


I'm not sure how you put 2 and 2 together to come up with Reggae. 
It seems to be an executable generator with a build 
configuration. It leaves it up to the user to come up with D code 
to figure out the build.


I'm talking about cloning phobos/druntime/dmd github repositories 
and automatically building them. No messing around with 
environment variables and such.

Re: Workaround for typeid access violation


On Thursday, 18 June 2015 at 14:11:42 UTC, ketmar wrote:

On Thu, 18 Jun 2015 12:08:10 +, Etienne Cimon wrote:


On Thursday, 18 June 2015 at 11:43:18 UTC, ketmar wrote:

On Wed, 17 Jun 2015 22:35:12 +, Etienne Cimon wrote:


e.g. __gshared MyObj g_obj1;

Thread 1: g_obj1 = new MyObj;
Thread 2: g_obj1.obj2 = new MyObj;
Thread 3: write(g_obj1.obj2); -- access violation (probably)


so no way to anchor the whole object tree by assigning it to 
__gshared root? sure, this will never make it into mainline.


__gshared is a little sketchy. We can have TLS GC by default 
by piping `new shared` to a shared GC. It's even safer, 
because then we have the type system helping out.


e.g. shared MyObj g_obj1;
Thread 1: g_obj1 = new shared MyObj;
Thread 2: g_obj1.obj2 = new shared MyObj;
Thread 3: write(g_obj1.obj2); -- success!


besides, wouldn't it break `std.concurrency`? (ketmar have to 
dig into code instead of asking...)


If it does, we fix it. I've never seen druntime/phobos mismatched 
versions (2.067  2.066) compiled together successfully, we 
shouldn't allow a necessary change to be blocked because of this 
alone.


As a workaround, you can also do __gshared MyObj g_obj1 = cast() 
new shared MyObj;

Re: Workaround for typeid access violation

2015-06-18 Thread Etienne Cimon via Digitalmars-d


On Thursday, 18 June 2015 at 15:43:10 UTC, Wyatt wrote:

On Thursday, 18 June 2015 at 15:19:19 UTC, Etienne wrote:

On Thursday, 18 June 2015 at 15:09:46 UTC, Wyatt wrote:

This comes to mind, along with the citations:
http://research.microsoft.com/en-us/um/people/simonpj/papers/parallel/local-gc.pdf

-Wyatt


That's exactly what we're talking about, but we do the work 
that was done by the globalisation policy by using the `new 
shared` keyword.


Maybe I misunderstood.  My interpretation was you were 
disallowing references from shared heap to local heap and
Exactly, unless you cast(shared) before you copy into the global 
heap - the local object must be kept trackable in the local heap 
or space. In any case, the shared is recursive and disallows 
this, so it's perfectly suitable to keep a shared GC consistent.


obviating the whole globalisation problem.  No migrations; just 
explicit marking of global objects with new shared. (Though 
I'm curious how you handle liveness of the global heap; it 
seems like that depends on information from each thread's 
allocator?)


The global heap and every thread will be scanned in stop the 
world setting just like the current GC. However, the idea is to 
use it less by making it exclusively for objects that were 
created with `new shared` `new immutable` `.idup` or `.sdup` (so 
that we can duplicate local objects into the shared GC 
conveniently)


In all of my security library (Botan) or TCP library (libasync) 
or even the vibe.d implementation at 
https://github.com/etcimon/vibe.d I haven't encountered a single 
instance of an object that was moved to another thread. The 
shared GC will be known to be very rarely useful.

Re: Martin Nowak is officially MIA


On Thursday, 18 June 2015 at 14:37:08 UTC, ketmar wrote:
dub is a build tool with an automatic dependency solver, it 
really shouldn't be called a package manager.


and it's not a build tool too. or, it's a build tool in the 
sense of bash is a build tool -- it can call external 
commands. Reggae is a build toold. dub is not a build tool.


It doesn't matter. Even if everything is locked into 
code.dlang.org or if you're using a custom shell in the dub.json 
to clone a git and use that path in the options, or if you're 
programming shell scripts for every OS. Any interface works as 
long as it does what it's supposed to do for the said package.


My point is, we need to be able to extend it to build and link an 
application with a custom druntime/phobos/dmd version from 
source. These libraries are the backbone of every application.

Re: Workaround for typeid access violation


On Thursday, 18 June 2015 at 15:09:46 UTC, Wyatt wrote:

On Wednesday, 17 June 2015 at 22:21:21 UTC, Laeeth Isharc wrote:


Do you have any links to reading material on this type of GC?


This comes to mind, along with the citations:
http://research.microsoft.com/en-us/um/people/simonpj/papers/parallel/local-gc.pdf

-Wyatt


That's exactly what we're talking about, but we do the work that 
was done by the globalisation policy by using the `new shared` 
keyword. We end up with a language that support the very 
foundation of what I'd say is the most solid Garbage Collection 
model.


To  summarise  these  results,  it  seems  that
although  the  local  heap  collector  performs  many  fewer  
young-
generation collections and fewer synchronisations, the benefits 
are
offset  to  some  extent  by  the  extra  work  being  done  by  
the  col-

lector to maintain the global-heap invariant. 

Globalising  the  entire  transitive  closure  was  on  average  
93%

slower, and results ranged from 7% faster to 577% slower.

A garbage collector with local per-processor heaps can outperform
a stop-the-world parallel garbage collector in raw parallel 
through-

put, and exhibits more robust performance through having fewer
all-core synchronisations.

Re: Martin Nowak is officially MIA


On Thursday, 18 June 2015 at 14:08:31 UTC, ketmar wrote:

On Thu, 18 Jun 2015 13:51:05 +, Etienne wrote:


On Thursday, 18 June 2015 at 12:37:15 UTC, Dragos Carp wrote:
On Thursday, 18 June 2015 at 02:22:13 UTC, Vladimir Panteleev 
wrote:
I would like to ask, what can we improve in our tooling and 
infrastructure to lessen the burden on release czars?


Merge dmd, druntime, phobos repos.


If I was release Czar, even DMD would just be a dub package. 
Let them be managed packages that can be selected by version, 
with many options! That, my friends, is the way.


but there is still no package manager, though. dub is not a 
package manager. and it's impossible to write one without 
scraping code.dlang.org too, as there is no API to get package 
list, or packages that was updated since the date.


Not every package manager has to provide binaries. We simply 
build the packages through dub. dub+dmd is a good source package 
manager in itself, we need to write a dub.json for 
dmd/druntime/phobos and make it possible to compile them through 
dub, then all is good

Re: Martin Nowak is officially MIA