No idea how it was harmful, but did you ever try compile blender after such
a cleanup? ;) There're lots of error: ‘return’ with a value, in function
returning void errors in MEM_freeN.
On Tue, May 21, 2013 at 1:37 PM, Campbell Barton ideasma...@gmail.comwrote:
Revision: 56936
I think the general populace has never understood this concept: We could
switch to a different cycle, with odd (unstable) and even (stable).
Things released with a version number are thought to be stable. Releasing
known unstable stuff under a number would just bring down the Blender image
of
Yep, compiled and checked it didn't crash or cause problems for basic usage.
Unfortunately I had WITH_GUARDEDALLOC off (from testing errors with
address sanitizer), so it didn't error out here,
I see Brecht's resolved the issue.
On Tue, May 21, 2013 at 7:03 PM, Sergey Sharybin
The link goes to 2.67 not 2.67a. Not sure if the file is new or what
but it is clearly not correct.
http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.67a
--
Douglas E Knapp
Creative Commons Film Group, Helping people make open source movies
with open source software!
The Get the latest release here leads to the download page on
blender.org, and is showing 267a here.
Try a Brower refresh.
Am 21.05.2013 20:35, schrieb Knapp:
The link goes to 2.67 not 2.67a. Not sure if the file is new or what
but it is clearly not correct.
On Tue, May 21, 2013 at 8:46 PM, Thomas Dinges blen...@dingto.org wrote:
The Get the latest release here leads to the download page on
blender.org, and is showing 267a here.
Try a Brower refresh.
Clicking the reload button did the trick. Sort of odd though. Thanks.
--
Douglas E Knapp
