skaller disse: [...]
> Yep. I understand. It's possible in principle to trace heaped > spaghetti stack frames inside Felix, since they're sure to have > Felix RTTI (which include the type name etc). > > The machine stack can't be traced by Felix, any more than > you can get one in C: if you want a snapshot of the stack > at some point you have to use a debugger like gdb or > Visual Studio: Felix generates C++ code. There's not much point tracing the machine stack in felix code as it's almost always trivial/one call deep. I think Artem would be referring to felix call chain traces. > Well two points: I personally do not use debuggers, stack traces, > or any other debugging aids .. I use print statements. The force is not quite with me, so I use printf and gdb's "bt" command. > Still other people like that stuff. Felix is in a better position > than many other systems, in that we can instrument the generated > code .. for example, to record function entry/exit. > > So many things could be done .. but it takes developer effort > to actually implement these things. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
