Hi guys. I don't know why but with CMakeVMMaker the asserts are not working. I can see the flags are being set correct in CmakeList.txt:<br><br>add_definitions(-arch i386 -mmacosx-version-min=10.5 -g3 -O0 -msse3 -funroll-loops -fasm-blocks -finline-functions -mfpmath=sse -march=pentium-m -falign-functions=16 -fno-gcse -fno-cse-follow-jumps -std=gnu99 -DBUILD_FOR_OSX -DUSE_INLINE_MEMORY_ACCESSORS -DLSB_FIRST -DHAVE_SYS_TIME_H -DHAVE_NANOSLEEP <span style="background-color:rgb(255, 255, 51)">-DNDEBUG=1</span> -DDEBUGVM=1 -DCOGMTVM=1 -DUSE_GLOBAL_STRUCT=0 -DBASE_HEADER_SIZE=4 -DCOGVM)<br>
<br>I modified the StackInterpreter to this:<br><br>lookupMethodInClass: class<br> | currentClass dictionary found |<br> <inline: false><br> self asserta: '42' = 'cuarenta y tres'.<br> self assert: 'mariano' = 'esta perdido'.<br>
self print: 'grrrr'; cr.<br>
<br>.....<br><br>and only 'grrr' is printed. The TWO previous assert are ignored. <br><br>I may be doing something very stupid...<br><br>thanks in advance,<br><br>Mariano<br><br><br><br><div class="gmail_quote">On Wed, Apr 13, 2011 at 8:06 PM, Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com" target="_blank">siguctua@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div><br>
On 13 April 2011 19:13, Mariano Martinez Peck <<a href="mailto:marianopeck@gmail.com" target="_blank">marianopeck@gmail.com</a>> wrote:<br>
> I've just commited the fix, but not the comment ;)<br>
><br>
> Seriously, I don't know how we can document this kind of things.<br>
> Putting such comments in #compilerFlagsRelease or #compilerFlagsRelease<br>
> doesn't make sense because they are aprox. 12 implementaions...I don't want<br>
> to copy paste to all of them. Only in one? it doesn't make sense because<br>
> people won't see it. So..how we document this kind of things? I have no<br>
> idea.<br>
><br>
> The same with class comments. There are so many classes that copy pasting or<br>
> documenting only one doesn't make sense.<br>
><br>
<br>
The root class is enough.<br>
A subclasses should just say something like 'i am special for<br>
___that__ and do things differently because i want __that__'.<br>
<br>
<br>
> The only thing I though is doing something like this:<br>
><br>
><br>
> compilerFlagsRelease<br>
> ^#('-g3' '-Os' '-fvisibility=hidden' '-funroll-loops' '-fasm-blocks'<br>
> '-finline-functions' '-mfpmath=sse' '-fomit-frame-pointer'<br>
> '-march=pentium-m' '-mtune=prescott' '-falign-functions=16' '-fno-gcse'<br>
> '-fno-cse-follow-jumps' '-std=gnu99' '-DBUILD_FOR_OSX'<br>
> '-DUSE_INLINE_MEMORY_ACCESSORS' '-DLSB_FIRST'<br>
> '-DUSE_INLINE_MEMORY_ACCESSORS' '-DHAVE_SYS_TIME_H' '-DHAVE_NANOSLEEP'<br>
> '-DNDEBUG=0' , self debugVMFlag: true, '-DCOGMTVM=0'<br>
> '-DUSE_GLOBAL_STRUCT=0' '-DBASE_HEADER_SIZE=4')<br>
><br>
>>>debugVMFlagEnable: boolean<br>
> "THIS flag is blagh...blh..."<br>
> ^ '-DDEBUGVM=', boolean asNumber asString<br>
><br>
> or something like that...<br>
><br>
><br>
<br>
This knowledge is important. It of course a question where to put that,<br>
but that's exactly why i didn't wanted to use autoconf to generate<br>
config.h file, which contains like 50 various flags,<br>
without any clues, where these flags being used, and in what<br>
situations they should be turned on or off..<br>
<br>
So, later we could step over every flag and properly document them,<br>
and like that, for people who will come later, we will have an idea<br>
what are need to deal with and why.<br>
<br>
> cheers<br>
><br>
> Mariano<br>
><br>
<br>
--<br>
Best regards,<br>
Igor Stasenko AKA sig.<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>