On Wed, Apr 11, 2018 at 08:45:15PM +, Dmitry Olshansky via
Digitalmars-d-announce wrote:
[...]
> What would have made contract trully powerful for me is them being
> emitted at caller side. This way if I use a release build of library
> but debugging my app I still get my stupidity guarded by
https://github.com/ZILtoid1991/pixelperfectengine/releases/tag/v0.9.4-alpha.2
The editor is almost usable (still needs a way to import tiles
from its own proprietary format), and now has a working, although
still a bit slow and unstable transformable tile layer with
mode7-esque capabilities.
On Friday, 6 April 2018 at 12:26:36 UTC, Mike Parker wrote:
Congratulations to Zach Tollen and everyone who worked on DIP
1009. It took a painful amount of time to get it through the
process, but it had finally come out of the other side with an
approval. The proposal itself was approved early
On Wednesday, 11 April 2018 at 09:45:07 UTC, Jonathan M Davis
wrote:
It's one thing for someone who is familiar with D to weigh the
options and decide that being tied to ldc is okay. It's quite
another to tell someone who isn't familiar with D that in order
to use D, they have to use a feature
On Wednesday, 11 April 2018 at 12:22:56 UTC, bachmeier wrote:
It also wouldn't work with GDC. Given that GDC has been added
to GCC, it would be a bad idea to tell people they need to use
LDC to work with C code.
Currently porting a project to linux, stuff is so severely
outdated, pretty much
11.04.2018 21:13, Adam D. Ruppe пишет:
On Wednesday, 11 April 2018 at 17:26:19 UTC, drug wrote:
That's it -
https://github.com/drug007/nanogui/tree/interacting_with_checkbox
So MouseEvent is sent on mouse motion too, and redrawing on each motion
might back up the queue.
Otherwise, nothing
On 4/11/2018 3:25 AM, Atila Neves wrote:
I did the best I could having seen some macros. It's likely there are cases I've
missed, or that maybe the translation in the link above doesn't work even for
what it's supposed to be doing (I have no confidence about catching all the C
casts for
On Wednesday, 11 April 2018 at 17:26:19 UTC, drug wrote:
That's it -
https://github.com/drug007/nanogui/tree/interacting_with_checkbox
So MouseEvent is sent on mouse motion too, and redrawing on each
motion might back up the queue.
Otherwise, nothing obvious jumps out at me so I might have
11.04.2018 16:59, Adam D. Ruppe пишет:
On Saturday, 7 April 2018 at 09:13:06 UTC, drug wrote:
https://github.com/drug007/nanogui
I would be glad if you take a look
Do you have a complete example I can just compile and run to get started?
That's it -
On Wednesday, 11 April 2018 at 16:16:33 UTC, Jonathan M Davis
wrote:
If we actually end up with a language improvement that makes it
so that contracts are compiled in based on the caller instead
of the callee, then I'll start using contracts. Until then, I'm
not generally going to bother.
My
On Wednesday, April 11, 2018 07:47:14 H. S. Teoh via Digitalmars-d-announce
wrote:
> On Tue, Apr 10, 2018 at 11:43:00PM -0600, Jonathan M Davis via
> Digitalmars-d-announce wrote: [...]
>
> > IMHO, for contracts to be worth much outside of the inheritance case,
> > we'd need to do something like
On Monday, 9 April 2018 at 11:03:48 UTC, Atila Neves wrote:
Here's my blog post about my project that allows directly
#including C headers in D*
https://atilanevesoncode.wordpress.com/2018/04/09/include-c-headers-in-d-code/
Cannot manage to build it on Windows:
D:\git\dpp>dub build
WARNING:
On Wed, Apr 11, 2018 at 05:23:58AM +, really? via Digitalmars-d-announce
wrote:
> On Friday, 6 April 2018 at 17:36:20 UTC, H. S. Teoh wrote:
> >
> > Yeah, I think having expression syntax will make contracts more
> > readable. We'll just have to see.
> >
>
> Sorry, but I fail to see how
On Tue, Apr 10, 2018 at 11:43:00PM -0600, Jonathan M Davis via
Digitalmars-d-announce wrote:
[...]
> IMHO, for contracts to be worth much outside of the inheritance case,
> we'd need to do something like make it so that contracts are compiled
> in based on whether the caller used -release or not
On Monday, 9 April 2018 at 11:03:48 UTC, Atila Neves wrote:
Here's my blog post about my project that allows directly
#including C headers in D*
I don't know the exact details of your project but can't you just:
1. Copy the includes
2. Paste them into a C file
3. Run DStep on the C file
4.
On Monday, 9 April 2018 at 11:03:48 UTC, Atila Neves wrote:
Here's my blog post about my project that allows directly
#including C headers in D*
BTW, you can steal the config script [1] from DStep to help
detect locations of LLVM/libclang. It also supports static
linking. Supports manually
11.04.2018 16:59, Adam D. Ruppe пишет:
Do you have a complete example I can just compile and run to get started?
Yes, but it needs to be pushed. I've ported Window, Widget, Label and
Checkbox (may be something else) and interacting by means of mouse
(clicking, motion and dragging). But it
AFAIK, GDC does not make it, so hopefully it will be merge with gcc 9
On Wed, Apr 11, 2018 at 3:44 PM, drug via Digitalmars-d-announce <
digitalmars-d-announce@puremagic.com> wrote:
> 11.04.2018 16:26, Uknown пишет:
>
> On Wednesday, 11 April 2018 at 13:17:23 UTC, drug wrote:
>>
>>> 11.04.2018
11.04.2018 16:30, bauss пишет:
The documentation should probably be updated to match ddoc.
Sure, of course, but it has low priority now. It is just proof of
concept. First of all I'm interested in estimation of changes I've made.
For example I'm trying to keep const qualifier as most as
On Saturday, 7 April 2018 at 09:13:06 UTC, drug wrote:
https://github.com/drug007/nanogui
I would be glad if you take a look
Do you have a complete example I can just compile and run to get
started?
11.04.2018 16:26, Uknown пишет:
On Wednesday, 11 April 2018 at 13:17:23 UTC, drug wrote:
11.04.2018 15:22, bachmeier пишет:
On Wednesday, 11 April 2018 at 09:45:07 UTC, Jonathan M Davis wrote:
... Given that GDC has been added to GCC...
Is it true? I don't see anything like that here
On Saturday, 7 April 2018 at 09:13:06 UTC, drug wrote:
https://github.com/drug007/nanogui
I would be glad if you take a look
The documentation should probably be updated to match ddoc.
On Wednesday, 11 April 2018 at 13:17:23 UTC, drug wrote:
11.04.2018 15:22, bachmeier пишет:
On Wednesday, 11 April 2018 at 09:45:07 UTC, Jonathan M Davis
wrote:
... Given that GDC has been added to GCC...
Is it true? I don't see anything like that here
https://gcc.gnu.org/gcc-8/changes.html
11.04.2018 15:22, bachmeier пишет:
On Wednesday, 11 April 2018 at 09:45:07 UTC, Jonathan M Davis wrote:
... Given that GDC has been added to GCC...
Is it true? I don't see anything like that here
https://gcc.gnu.org/gcc-8/changes.html
On Wednesday, 11 April 2018 at 09:45:07 UTC, Jonathan M Davis
wrote:
It's one thing for someone who is familiar with D to weigh the
options and decide that being tied to ldc is okay. It's quite
another to tell someone who isn't familiar with D that in order
to use D, they have to use a
On Tuesday, 10 April 2018 at 14:00:49 UTC, WebFreak001 wrote:
What about workspaces?
Multi workspaces in vscode aren't implemented yet though.
By multi workspaces, do you mean a multi-root workspace ? If so,
multi-roots arrived with LSP 3.6.0 / vscode-languageclient 3.4.0
(if you meant
On Wednesday, 11 April 2018 at 06:24:38 UTC, Jacob Carlborg wrote:
On Monday, 9 April 2018 at 11:03:48 UTC, Atila Neves wrote:
Here's my blog post about my project that allows directly
#including C headers in D*
https://atilanevesoncode.wordpress.com/2018/04/09/include-c-headers-in-d-code/
On Wednesday, 11 April 2018 at 06:21:47 UTC, Jacob Carlborg wrote:
On Tuesday, 10 April 2018 at 23:44:46 UTC, Atila Neves wrote:
The beauty of using libclang is that name mangling issues
don't exist. :)
How is that not going to be an issue? Are you adding
`pragma(mangle)` everywhere?
Yes.
On Wednesday, 11 April 2018 at 06:12:49 UTC, rikki cattermole
wrote:
On 09/04/2018 11:03 PM, Atila Neves wrote:
Here's my blog post about my project that allows directly
#including C headers in D*
https://atilanevesoncode.wordpress.com/2018/04/09/include-c-headers-in-d-code/
The summary is
On Wednesday, April 11, 2018 09:23:29 Kagamin via Digitalmars-d-announce
wrote:
> On Monday, 9 April 2018 at 19:36:23 UTC, Atila Neves wrote:
> > If you add to all that "No, really, it's ok, there's this
> > project that forked one of the compilers. No, it's not the
> > reference compiler.
On Monday, 9 April 2018 at 19:36:23 UTC, Atila Neves wrote:
If you add to all that "No, really, it's ok, there's this
project that forked one of the compilers. No, it's not the
reference compiler. There's just this bit of non-standard
syntax to learn that's neither C nor D", then the chances
On Tuesday, 10 April 2018 at 08:46:55 UTC, John Colvin wrote:
Available now on homebrew :)
Thanks
I try to keep homebrew up to date with the latest betas, but
the stats show that almost no-one ever downloads them, despite
reasonable numbers getting the stable version. See for example
On Monday, 9 April 2018 at 11:03:48 UTC, Atila Neves wrote:
Here's my blog post about my project that allows directly
#including C headers in D*
https://atilanevesoncode.wordpress.com/2018/04/09/include-c-headers-in-d-code/
How do you deal with macros containing invalid D code, i.e.
On Tuesday, 10 April 2018 at 23:44:46 UTC, Atila Neves wrote:
The beauty of using libclang is that name mangling issues don't
exist. :)
How is that not going to be an issue? Are you adding
`pragma(mangle)` everywhere?
--
/Jacob Carlborg
On 09/04/2018 11:03 PM, Atila Neves wrote:
Here's my blog post about my project that allows directly #including C
headers in D*
https://atilanevesoncode.wordpress.com/2018/04/09/include-c-headers-in-d-code/
The summary is that, modulo bugs, things like this work:
#include
void
35 matches
Mail list logo
