Search found 367 matches

Just for the record, github supports readme files in the markdown format (and possibly others as well). This will allow you to format the code example a bit.

I was going to document each package as I ported it so as not to be in the situation I'm in with Derelict2. But I hate documentation! So I'll just port first.

It's a good idea but it doesn't work v ...

I've been thinking some more on this issue. I'm wondering if it has anything to do with what the documentation for NSAutoreleasePool says:

You should always drain an autorelease pool in the same co ...

That was to be able to support both D1 and D2 in the same source file. He's dropping the D1 support, if I understand everything correctly.

Hmm, I'm wondering if it would be possible to use the C main or D main function to get around that extra "main" function.

Sounds good. It will be a lot easier than porting the Objective-C code to D, Objective-C bindings are really verbose.

I guess we need to port those files and add them to the bindings.

Joels-MacBook-Pro:jecax joelcnz$ dmd example.d
Joels-MacBook-Pro:jecax joelcnz$ ./example
objc[352]: Object 0x10901e710 of class __NSCFString autoreleased with no pool in place - ...

I don't think it will leak, or it depends on how you see it. The clean up happens when the application quits and then the OS will reclaim the memory anyway.

The garbage collector in Mac OS X is optional and disabled by default (if I recall correctly).

I've been trying quite a while now to find a solution for this problem but unfortunately I haven't.

Since the application will quit just after these "release" methods have been called and ...

When I choose to build frameworks it produces these files:
doob@doob ~/Downloads/allegro/Build/lib $ ls -l
total 0
drwxr-xr-x 6 doob staff 204 4 Jan 21:05 Allegro-5.1.framework
drwxr-xr-x ...

I just compiled Allergo 5.1.0 and it outputs these files:

doob@doob ~/Downloads/allegro/Build/lib $ ls -l
total 3264
-rwxr-xr-x 1 doob staff 1052180 4 Jan 20:50 liballegro.5.1.0.dylib
l ...

If you still want to be able to checkout individual packages, git submodules would make that possible. A git submodule is basically a separate repository with its own history included in another repos ...

Now that it is possible to interface to C++, there are any plans to make the SFML binding "correct" which means that it can use as SFML in C++ with Classes and Objects?
I tried in the past ...