On Tuesday, 12 December 2017 at 06:27:30 UTC, Ivan Trombley wrote:
This isn't a scaling problem (which is totally solved by
Scaling is not a prerequisite for this problem.
pre-multiplying the alpha with the colors BTW). This is a gamma
How did you this? Using editor or using shader? If shder,
On Tuesday, December 05, 2017 20:11:33 Walter Bright via Digitalmars-d
wrote:
> https://help.github.com/articles/basic-writing-and-formatting-syntax/
>
> Anyone interested in picking up the flag?
>
> (I know this has come up before, and I've been opposed to it, but I've
> changed my mind.)
I conf
On Tuesday, 12 December 2017 at 03:34:51 UTC, Dmitry wrote:
On Tuesday, 12 December 2017 at 03:32:05 UTC, Ivan Trombley
wrote:
It turns out that it's an issue with the color channels being
in sRGB color space and the alpha channel being linear. I
verified this by doing a software blend of the i
On Monday, 11 December 2017 at 15:45:07 UTC, Guillaume Piolat
wrote:
On Monday, 11 December 2017 at 14:22:37 UTC, Jakob Bornecrantz
wrote:
And to add more, CommonMark on the other hand has a full spec
written and several test that covers the difficult to get
right parts of Markdown/CommonMark
Thanks, I will try that.
On Mon, Dec 11, 2017 at 7:34 PM, German Diago via Digitalmars-d <
digitalmars-d@puremagic.com> wrote:
> On Thursday, 7 December 2017 at 14:09:35 UTC, Steven Schveighoffer wrote:
>
>> On 12/7/17 6:46 AM, Daniel Kozak wrote:
>>
>>> Not much helpful, still does not know whic
On Tuesday, 12 December 2017 at 02:30:39 UTC, Walter Bright wrote:
It's apparently written in Volt:
https://github.com/VoltLang/Watt
But the two links there to Volt are dead:
https://github.com/VoltLang/Watt/blob/master/volt-lang.org
Ah, the joys of forgetting too ensure URLs in Markdown REA
On Tuesday, 12 December 2017 at 03:32:05 UTC, Ivan Trombley wrote:
It turns out that it's an issue with the color channels being
in sRGB color space and the alpha channel being linear. I
verified this by doing a software blend of the images and then
doing another software blend using gamma corr
It turns out that it's an issue with the color channels being in
sRGB color space and the alpha channel being linear. I verified
this by doing a software blend of the images and then doing
another software blend using gamma corrected values.
There's a setting in opengl to correct for it,
glEn
On Friday, 8 December 2017 at 09:33:03 UTC, Ali Çehreli wrote:
I'm trying to use D as a library to be called from a non-D
environment e.g. Java runtime. If I'm not mistaken, it's quite
difficult and perhaps impossible to use GC in such a scenario.
It works as long as attached threads don't go a
On 12/11/2017 2:30 PM, Jakob Bornecrantz wrote:
It is not written in D, but the language is close enough in concepts that it can
be mechanically ported into D, and is licensed under BOOST. Feel free to do what
ever to it[1].
Thank you for Boost licensing it!
We first used the markdown parser
On 12/11/2017 2:30 PM, Jakob Bornecrantz wrote:
What I'm trying to get at is, use the testsuit and spec, it will save you lot of
other problems down the road. And you will be making the world of Markdown a
better place because there will be one less implementation that does things
slightly diff
On Tuesday, 17 May 2016 at 08:51:01 UTC, Jacob Carlborg wrote:
As an alternative to glibc there's a C standard library called
musl [1]. This is the C standard library used by ELLCC [2], a
cross-compiler based on Clang. This cross-compiler makes it
very easy to target other platforms and can be
On 12/11/2017 08:58 AM, Mengu wrote:
> On Monday, 11 December 2017 at 16:25:42 UTC, Ali Çehreli wrote:
>> On 12/08/2017 02:54 AM, Nemanja Boric wrote:
>>> [...]
>>
>> So, in cases where D is just a portable library, the only sane thing
>> to do seems to be what Kagamin suggested: create a D thread
On Monday, 11 December 2017 at 23:24:02 UTC, Ali Çehreli wrote:
Since I don't have access to Windows, OS X, etc. systems nor
have I expertise in them, I don't trust myself to write
core.thread tests for anything but Posix.
What to do for non-Posix systems? I'm tempted to wrap the
entire test
Since I don't have access to Windows, OS X, etc. systems nor have I
expertise in them, I don't trust myself to write core.thread tests for
anything but Posix.
What to do for non-Posix systems? I'm tempted to wrap the entire test
code with version(Posix) but it will give the wrong impression th
On 2017-12-10 22:00, Timothee Cour wrote:
Is it on the roadmap? It's been a very long standing issue.
I don't think it's on the roadmap. Nobody has needed it badly enough to
implement it. I could probably give it a shot if someone implements
constructors, i.e. __attribute__((constructor)), w
On Monday, 11 December 2017 at 20:45:38 UTC, Walter Bright wrote:
On 12/11/2017 6:22 AM, Jakob Bornecrantz wrote:
There are loads of implementations of CommonMark
https://github.com/commonmark/CommonMark/wiki/List-of-CommonMark-Implementations
They appear to be libraries that offer an implemen
On 12/11/17 1:45 PM, Walter Bright wrote:
On 12/11/2017 6:22 AM, Jakob Bornecrantz wrote:
There are loads of implementations of CommonMark
https://github.com/commonmark/CommonMark/wiki/List-of-CommonMark-Implementations
They appear to be libraries that offer an implementation. Does the
Mark
I realize that I focused too much on the how, and not enough on
the why.
By "metadata" I mean the data that is "just there" in any object,
in addition to user defined fields.
An example of per-class metadata is the pointer to the the
virtual function table. It is installed by the compiler or
On 12/11/2017 6:22 AM, Jakob Bornecrantz wrote:
There are loads of implementations of CommonMark
https://github.com/commonmark/CommonMark/wiki/List-of-CommonMark-Implementations
They appear to be libraries that offer an implementation. Does the Markdown used
in github, reddit, wikipedia, doxy
On 12/11/2017 11:29 AM, John Gabriele wrote:
Right. That said, if you want to add a handful of markdown-ish features, I think
it would be most useful to draw your very limited markdown subset from the
CommonMark markdown spec. The other option takes you down the road of
unintentionally creating
I just had a discussion with Walter, Andrei and Ali about open
methods. While Andrei is not a great fan of open methods, he
likes the idea of improving D to better support libraries that
extend the language - of which my openmethods library is just an
example. Andrei, correct me if I misreprese
On Monday, 11 December 2017 at 00:54:00 UTC, Walter Bright wrote:
Don't get me wrong, I think commonmarkdown is a worthy effort,
and is definitely in the running to be a standard. Certainly a
lot more effort seems to have been put into it vs other
markdowns.
Note that CommonMark isn't simply
On Monday, 11 December 2017 at 15:45:07 UTC, Guillaume Piolat
wrote:
The CommonMark approach is to just take the union of all
possible features and call it a day.
Standards without opinions don't deserve to be implemented by
anyone.
I disagree. If anything, it's more of a subset of features
On Thursday, 7 December 2017 at 14:09:35 UTC, Steven
Schveighoffer wrote:
On 12/7/17 6:46 AM, Daniel Kozak wrote:
Not much helpful, still does not know which compiler flags
have been used, or how I can reproduce this. It would be nice
to have some shell script which will compile it and run it i
Is anyone out there interested in Dub support for D builds using SCons?
If there is, then I have begun to do a bit more work on
https://github.com/russel/SCons_D_Experiment
and would be pleased to have others helping ready the dub.py tool and it's
tests to get into the SCons distribution.
--
On Monday, 11 December 2017 at 15:45:07 UTC, Guillaume Piolat
wrote:
On Monday, 11 December 2017 at 14:22:37 UTC, Jakob Bornecrantz
wrote:
And to add more, CommonMark on the other hand has a full spec
written and several test that covers the difficult to get
right parts of Markdown/CommonMark
On Monday, 11 December 2017 at 14:22:37 UTC, Jakob Bornecrantz
wrote:
There are loads of implementations of CommonMark
https://github.com/commonmark/CommonMark/wiki/List-of-CommonMark-Implementations the one I have written is not listed. That covers 1 and 2.
Also Markdown is not a standard, i
On Monday, 11 December 2017 at 16:25:42 UTC, Ali Çehreli wrote:
On 12/08/2017 02:54 AM, Nemanja Boric wrote:
[...]
So, in cases where D is just a portable library, the only sane
thing to do seems to be what Kagamin suggested: create a D
thread and send requests to it.
That way, we would be
On Monday, 11 December 2017 at 04:57:44 UTC, Ivan Trombley wrote:
Experimenting with compositing images in SDL2, I get a dark
edge around my textures. In the image below, you can see the
top example where I composite the cyan image on top of the
blue/magenta image looks correct but the bottom e
On 12/08/2017 02:54 AM, Nemanja Boric wrote:
On Friday, 8 December 2017 at 09:33:03 UTC, Ali Çehreli wrote:
5) We depend on SIGUSR1 (and SIGUSR2, which may not be necessary but
it's a different topic) to suspend non-D threads. Does that work with
all threads? What if the calling framework has o
On Monday, 11 December 2017 at 14:22:37 UTC, Jakob Bornecrantz
wrote:
And to add more, CommonMark on the other hand has a full spec
written and several test that covers the difficult to get right
parts of Markdown/CommonMark. I'm sure I don't need to tell you
the virtues of a good test suit.
On Monday, 11 December 2017 at 00:54:00 UTC, Walter Bright wrote:
On 12/10/2017 6:22 AM, meppl wrote:
I think these are wrong criterias to estimate the value of
commonmark. Commonmark doesn't need to list anyone and doesn't
need to be listed by anyone to be a standard. commonmark is a
standard
On Monday, 11 December 2017 at 04:57:44 UTC, Ivan Trombley wrote:
Experimenting with compositing images in SDL2, I get a dark
edge around my textures. In the image below, you can see the
top example where I composite the cyan image on top of the
blue/magenta image looks correct but the bottom e
On 12/08/2017 04:23 AM, Guillaume Piolat wrote:
>> Every D api call must call thread_attachThis
> I advise to make a RAII struct you will put in any accessible
callback, which deals with this
Of course. :) That's how I've been trying to use.
> IMHO thread_detachThis *must* be called at entry
On 12/08/2017 02:53 AM, Kagamin wrote:
You can create a D thread an send request to it.
That's a good idea. Thanks.
Ali
On Friday, 8 December 2017 at 07:54:11 UTC, Suliman wrote:
I found very interesting project
https://github.com/hioa-cs/IncludeOS
But by description it's target to C++ "IncludeOS is an
includable, minimal unikernel operating system for C++ services
running in the cloud".
I think that would b
On Saturday, 9 December 2017 at 05:07:46 UTC, Elronnd wrote:
Note to anyone trying to implement this (I might try, but I
don't have the expertise to...):
http://wiki.osdev.org/D_Bare_Bones,
http://wiki.osdev.org/D_barebone_with_ldc2, and
https://github.com/PowerNex/PowerNex
None of D's OSes
On Monday, 11 December 2017 at 07:04:19 UTC, Mike Parker wrote:
On Monday, 11 December 2017 at 04:57:44 UTC, Ivan Trombley
wrote:
Any SDL experts out there that can give me a clue?
I've used SDL quite a bit, but can't help with your specific
problem. However, I suggest you try the new(ish)
39 matches
Mail list logo
