You should fix your LICENSE following these instructions
http://www.gnu.org/licenses/gpl-howto.html. I hope you understand
the virality of GPL and why most people won't touch your code for
real work.
On Wednesday, 20 November 2013 at 07:48:21 UTC, Mineko wrote:
Yo, I'm starting off a new
Why not stick with scipy+numpy in python? Writing numerical code
is painfully time consuming. It's also unlikely that your code
will be more performant than those libraries', it takes a lot of
expertise.
On Thursday, 17 October 2013 at 20:31:38 UTC, Yura wrote:
Dear D programmers,
I am
Not really intrinsic to the language(syntactically), but there is
the soft realtime GC, meaning you can control when and for how
long the gc can do the collecting. Sounds like a lovely feature
for games.
http://nimrod-code.org/gc.html
On Friday, 23 August 2013 at 17:33:12 UTC, Ramon wrote:
I
On Saturday, 29 June 2013 at 08:47:14 UTC, Paulo Pinto wrote:
Maybe some help from proper Portuguese as well? :)
--
Paulo
Ei gajo, did you mean weird portuguese? :P
Maybe Dr. Memory could work out well as an alternative to
valgrind with this issue?
http://www.drmemory.org/
On Saturday, 22 June 2013 at 21:41:15 UTC, Walter Bright wrote:
Compiling std.algorithm for unittests consumes all the memory
on many machines. I've been looking into what is allocating
If just installing VC++ doesn't work...
http://forum.dlang.org/post/mailman.2800.1355837582.5162.digitalmar...@puremagic.com
On Saturday, 22 June 2013 at 04:28:57 UTC, Jonathan Dunlap wrote:
On Friday, 21 June 2013 at 23:04:10 UTC, Walter Bright wrote:
On 6/21/2013 3:43 PM, Jonathan Dunlap
On Sunday, 16 June 2013 at 02:12:02 UTC, Geancarlo Rocha wrote:
I expected the memory to ramp up in the first couple iterations
and eventually reach a stable point, but for some reason,
windows task manager shows it increases on every iteration.
Compiling with -m64 doesn't seem to change
On Sunday, 16 June 2013 at 18:02:26 UTC, Timon Gehr wrote:
On 06/16/2013 07:20 PM, Geancarlo Rocha wrote:
On Sunday, 16 June 2013 at 02:12:02 UTC, Geancarlo Rocha wrote:
I expected the memory to ramp up in the first couple
iterations and
eventually reach a stable point, but for some reason
I expected the memory to ramp up in the first couple iterations
and eventually reach a stable point, but for some reason, windows
task manager shows it increases on every iteration. Compiling
with -m64 doesn't seem to change this issue.
http://pastebin.com/G5JXR9AA
On Thursday, 30 May 2013 at 15:05:40 UTC, monarch_dodra wrote:
I could be mistaken, but those languages don't have the notion
of declaration, do they? (honest question)
Last time I tried a similar language, basically, any variable
name that is not yet used is resolved to null. Which is why
That's julia's(http://julialang.org/) goal, but of course it's
not nearly polished.
I'm interested in this as well, since I'm not totally comfortable
about using a pirated MATLAB version and I hear that numpy can't
match its performance on macro code.
In C#, they have introduced automatic properties for that purpose
of initial encapsulation:
public int i { get; set; } //get and set can be modified with
private etc
Then the getter and setter methods are automatically implemented.
I'm not closely following the discussions involved in the
12 matches
Mail list logo