Re: Visual D 0.3.37 released

2013-11-12 Thread Rainer Schuetze


Sorry for the delay, I've been away for a couple of days.

On 07.11.2013 07:13, Alexander Bothe wrote:

On Thursday, 7 November 2013 at 05:45:34 UTC, Rainer Schuetze wrote:


Yeah, being able to get releases out more often, and having bug fixes
being tested in the field would be nice. But I think we should not
over-engineer things here.
Do you have a web-server that could do the compilation?


No - I just have got a normal dedicated web-server thingy for phpmysql ^_^

But well, just a very small infrastructure that allows us to update
software more often - a couple of hours ago I implemented this new
eponymous template syntax..and now you had to release another VisualD to
have it in there, right?


ATM, yes. Maybe we can create a small update installer for the DParser 
component that you could also build.


Another option might be to get a time slot on the auto tester build 
servers. I could try to prepare a script to do a Visual D build from the 
necessary branches. Brad, would that be possible?




Re: Visual D 0.3.37 released

2013-11-12 Thread Rainer Schuetze



On 10.11.2013 08:13, Nicholas Londey wrote:

Have a look at this and see if that helps. I think I got it working in
vs2013 because it was the announcement that it should be working that
prompted me to find out why it wasn't.

http://d.puremagic.com/issues/show_bug.cgi?id=11457


Unfortunately the beta test has been done with the 8.0 Widows SDK only, 
and Microsoft changed their library paths again with the 8.1 SDK.


Re: Visual D 0.3.37 released

2013-11-12 Thread Rainer Schuetze



On 12.11.2013 08:25, evilrat wrote:

On Sunday, 10 November 2013 at 08:53:08 UTC, evilrat wrote:

ok i forgot about output pane. so what i see here...

ConsoleApp1\Debug\ConsoleApp1.pdb: cannot load PDB helper DLL


so the problem with debug server formats?
i wish it would work with visual studio 2013 soon, but at least x64
debug works so i can continue using it for now \0/


This message is emitted by cv2pdb that is used to convert the debug 
information to a pdb file. Unfortunately cv2pdb is not yet updated for 
VS2013. I haven't tried it, but a workaround might be to copy the file 
vc\bin\mspdb120.dll to mspdb110.dll.


If you switch the debugger to Mago, the conversion is no longer 
needed, so you can still build and debug Win32 executables.


Re: dchip is a D2 port of the Chipmunk2D physics library for 2D games

2013-11-12 Thread Andrej Mitrovic
On 11/12/13, Sergei Nosov sergei.no...@gmail.com wrote:
 For some reason, DMD (v2.064.2) fails to compile with that flag.
 The error is:
 Internal error: ../ztc/cg87.c 331
 Error: DMD compile run failed with exit code 1

Aww. If only dub knew how to automatically run dustmite.

 LDC slows down for about 20-25%.

Interesting. Thanks.

Btw, how did you make dub use a -version flag anyway? I can't figure
it out from the docs. I suppose it's something like:

dub --build=release --version=?

But I see that --version means something else in dub.


Re: dchip is a D2 port of the Chipmunk2D physics library for 2D games

2013-11-12 Thread Dicebot
On Tuesday, 12 November 2013 at 15:39:27 UTC, Andrej Mitrovic 
wrote:
Btw, how did you make dub use a -version flag anyway? I can't 
figure

it out from the docs. I suppose it's something like:

dub --build=release --version=?

But I see that --version means something else in dub.


It is done via package.json modification, for whole project or 
some specific configurations : code.dlang.org/package-format


Also: Note that setting the DFLAGS environment variable will 
override the build type with custom flags. (c) dub


Re: dchip is a D2 port of the Chipmunk2D physics library for 2D games

2013-11-12 Thread Sönke Ludwig
Am 12.11.2013 16:55, schrieb Dicebot:
 On Tuesday, 12 November 2013 at 15:39:27 UTC, Andrej Mitrovic wrote:
 Btw, how did you make dub use a -version flag anyway? I can't figure
 it out from the docs. I suppose it's something like:

 dub --build=release --version=?

 But I see that --version means something else in dub.
 
 It is done via package.json modification, for whole project or some
 specific configurations : code.dlang.org/package-format
 
 Also: Note that setting the DFLAGS environment variable will override
 the build type with custom flags. (c) dub

Beat me to it... again ;)

Correction of my previous reply:

DFLAGS=-release -O -inline -version=CHIP_USE_DOUBLES dub


Re: Static Parameter Function Specialization in D

2013-11-12 Thread John J

On 11/11/2013 11:56 AM, Nordlöw wrote:

Can I move or delete this post?



I use Thunderbird and it's pretty easy to cancel my own messages:
Just select the post, go to 'Message' menu and click 'Cancel message'

The 'Delete' option is different though, it just deletes the message 
from your local computer while it still exists in the newsgroup for 
others to see.


Re: Static Parameter Function Specialization in D

2013-11-12 Thread Dicebot

On Tuesday, 12 November 2013 at 22:17:46 UTC, John J wrote:

On 11/11/2013 11:56 AM, Nordlöw wrote:

Can I move or delete this post?



I use Thunderbird and it's pretty easy to cancel my own 
messages:
Just select the post, go to 'Message' menu and click 'Cancel 
message'


It will actually send a new message that says that previous one 
should be discarded. Some mail servers / clients can be 
configured to respect that request but I'd be surprised to see 
that for NG.


Re: Visual D 0.3.37 released

2013-11-12 Thread Rainer Schuetze



On 12.11.2013 10:19, evilrat wrote:

On Tuesday, 12 November 2013 at 08:06:24 UTC, Rainer Schuetze wrote:

If you switch the debugger to Mago, the conversion is no longer
needed, so you can still build and debug Win32 executables.


mago gives cannot launch debugger on %appname%. hr = 897..., so only
x64 debugger left for usage


Are you sure that you are not trying to debug a 64-bit executable with 
mago? Maybe the working directory is invalid, this can also cause problems.


If it still fails, please show the full error code, maybe I can guess 
what's going wrong.