28.09.2012 20:47, Peter Alexander пишет:
On Friday, 28 September 2012 at 09:43:34 UTC, Timur Gafarov wrote:
dlib is a growing collection of native D language libraries serving as
a framework for various higher-level projects - such as game engines,
rendering pipelines and multimedia applications
On Fri, 28 Sep 2012 18:20:12 -0700
Brad Roberts wrote:
> On Fri, 28 Sep 2012, Walter Bright wrote:
>
> > True, but I would never write code that tried to throw an exception
> > across language boundaries, anyway. It's just asking for trouble.
>
> And that's fine for your code, but if you want D
On Saturday, September 29, 2012 06:41:01 Nick Sabalausky wrote:
> On Fri, 28 Sep 2012 18:20:12 -0700
>
> Brad Roberts wrote:
> > On Fri, 28 Sep 2012, Walter Bright wrote:
> > > True, but I would never write code that tried to throw an exception
> > > across language boundaries, anyway. It's just
On 2012-09-28 19:47, Peter Alexander wrote:
A note on your Vector implementation. Currently you use the vector
operators, e.g.
Vector!(T,size) opAddAssign (Vector!(T,size) v)
body
{
arrayof[] += v.arrayof[];
return this;
}
This is fine for large vectors, b
I think the original intent behind D's c++ support was just to make it
easier to work with c++. In other words your c++ come shouldn't throw
exceptions to D anyway.
So with golang you have to write a C wrapper. With D you can use c++.
On Sep 29, 2012 2:55 PM, "Jacob Carlborg" wrote:
>
> On 2012-09-28 19:47, Peter Alexander wrote:
>
>> A note on your Vector implementation. Currently you use the vector
>> operators, e.g.
>>
>> Vector!(T,size) opAddAssign (Vector!(T,size) v)
>> body
>> {
>> arrayof[] += v.a
On 2012-09-29 03:20, Brad Roberts wrote:
And that's fine for your code, but if you want D and DMD to be a system
that people use for larger systems, then cutting down the sheer number of
things that don't work when pushed is kinda important.
Exactly, I completely agree.
--
/Jacob Carlborg
On 2012-09-29 03:01, Walter Bright wrote:
True, but I would never write code that tried to throw an exception
across language boundaries, anyway. It's just asking for trouble.
If everything is working correctly and is compatible it shouldn't be any
problems.
--
/Jacob Carlborg
On 9/29/12, Jacob Carlborg wrote:
> On 2012-09-29 03:01, Walter Bright wrote:
>
>> True, but I would never write code that tried to throw an exception
>> across language boundaries, anyway. It's just asking for trouble.
>
> If everything is working correctly and is compatible it shouldn't be any
>
On 28-Sep-12 21:47, Peter Alexander wrote:
On Friday, 28 September 2012 at 09:43:34 UTC, Timur Gafarov wrote:
dlib is a growing collection of native D language libraries serving as
a framework for various higher-level projects - such as game engines,
rendering pipelines and multimedia applicatio
On 29-Sep-12 20:39, Dmitry Olshansky wrote:
On 28-Sep-12 21:47, Peter Alexander wrote:
On Friday, 28 September 2012 at 09:43:34 UTC, Timur Gafarov wrote:
dlib is a growing collection of native D language libraries serving as
a framework for various higher-level projects - such as game engines,
On 2012-09-29 18:08, Andrej Mitrovic wrote:
Also how are we supposed to control when a C++ library throws? We
could wrap every single function wrapper with a try/catch, but won't
this create a massive slowdown?
I'm not sure but I don't think so. As I understand it, DWARF on Posix
and SEH on W
On 9/29/12, Jacob Carlborg wrote:
> I'm not sure but I don't think so. As I understand it, DWARF on Posix
> and SEH on Windows are zero-cost exception handling systems. This means
> that there will be no performance loss at runtime as long as no
> exception is thrown. setjmp/longjmp on the other d
On Saturday, 29 September 2012 at 19:21:59 UTC, Jacob Carlborg
wrote:
I'm not sure but I don't think so. As I understand it, DWARF on
Posix and SEH on Windows are zero-cost exception handling
systems.
Only the x64 variant of SEH is "zero-cost". On x86, exception
handlers must be installed int
14 matches
Mail list logo
