I try to understand how to use the debug mode in wxmaxima. In the documentation is specified "See MACDOC;TRDEBG USAGE for more information. Consult GJC for more help".
I can't find the reference to "MACDOC;TRDEBG USAGE" nor "GJC". Could you help me please?
Wow, that's a good one. I believe GJC is George J. Carrette (?) who worked on Macsyma (the precursor to Maxima) about 40 years ago. MACDOC;TRDEBUG USAGE is a reference to a file on an ancient filesystem. There may be a file named trdebug.usg or something like that floating around; I haven't looked.
I think you will find most or all of the existing documentation for debugging in the section titled "Debugging" in the reference manual. Here it is online: http://maxima.sourceforge.net/docs/manual/maxima_38.html I think that the same documentation is also included in wxMaxima.
By the way, where did you find the reference to MACDOC?
Related
I just compiled code using the compiler option "-frecord-gcc-switches" to see which options the compiler selects automatically. Now I can see the options in section .GCC.command.line. There are several plausible compiler options but also one I cannot find any documentation about. What does -auxbase-strip png.o mean. Obviously it does something with png.o, but what does it do exactly?
Google search shows:
Hei Chan:
I am trying to find the document for auxbase and auxbase-strip,
but I can't find any.
Ian Lance Taylor:
They are internal options used to support the -fcompare-debug options.
They are not intended to be used by end users.
So, if you really want to know what this option does, you'll need to read GCC source (but you shouldn't care).
Hello, i want to start running some microbenchmarks on Apples Swift-language.
However i feel it is hard to find proper documentation for the different options in regards of compiler optimization.
I have read a lot of questions and articles about other peoples microbenchmarks of the language, however it would be nice to have some firm documentation on the subject.
In the latest beta, the ones to use seems to be:
-Onone
No optimizations
-O
Safe optimizations?
-Ounchecked (Replaced -Ofast)
Unsafe optimizations, (No checks for integer overflow, array out of bounds etc)
My question is, are these all my possible options? And does anybody have some resource that documents this?
EDIT:
I have found similar documention to the one i need about objective-c with gcc here:
https://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_2.html section 2.8. This is what i need for Swift..
I was reading about TCL's coding style - at wiki.tcl.tk - and I can't think of a reason for one of the recommendations.
A header comment should be in the form:
# tcl::HistRedo --
#
...
proc tcl::HistRedo {{event -1}} {
...
}
And it stresses
Follow the syntax [...] exactly [namely the] double-dash after the procedure name
My question is, what is the point of that double dash? Or similarly, what would go wrong, or not as good, without them? As in:
# tcl::HistRedo
#
Disclaimer This is largely guesswork and I may well be shot down in flames later by someone who actually knows...
I suspect that the coding style on the wiki is the style used in the Tcl sources, and the stressed instruction to follow the syntax exactly is addressed to people who maintain those sources.
If you failed to follow that syntax exactly, I suspect that a number of tools that I speculate have been written to do interesting things(tm) :-) with and to the sources wouldn't find the proc definition.
I'm pretty certain that there would be no functional effect.
The Win32_Thread class is described in MSDN here:
http://msdn.microsoft.com/en-us/library/aa394494(v=VS.85).aspx
Problem is, the definitions for the ThreadWaitReason attribute are concise, to say the least. Has anyone got any (more) verbose definitions?
Please, no purile MS bashing - even Mark Russinovich "Inside Windows..." series doesn't enumerate them!
Here's hoping
Simon
Does this page help?
Note that Windows has never done anything with these values, they're strictly informational for debugging purposes. So, probably why you don't find much info about them.
-scott
Is there a documentation system which is simple, will generate some friendly, hyperlinked documentation, for any language through the use of comment indications? Such a system may merely be given regexes or patterns to recognise comments and then generate structure.
I was going to write one but figured there must be one already.
Have you seen Doxygen? It may be what you're looking for.