When typing a function in the Spyder editor, such as fcn(, I find that Spyder often automatically barfs the entire function signature into the editor. This is especially unhelpful when instantiating a dataclass object--Spyder evidently still cannot read the dataclass fields--and even less helpful when using annotations, which I do frequently. How do I disable this feature? I'm using Spyder 4.1.1.
You can try this:
In Tools > Preferences > Completion and Linting > Advanced and disable Enable fallback completions and Enable code completion
Or in Tools > Preferences > Editor > Code introspection and uncheck what options you don't want.
Related
I have a problem when i'm using static functions because after rebuild/build the compiler does not generate the object code of this functions ( i see that because assembler code of this functions is not generated in .lss file ). How can i disable compiler optimization to avoid this issue.
Apparently the link above is broken/no longer pointing to the document. To help others (and my future self):
Disable Optimization in Atmel Studio / Microchip Studio:
Open the properties for the current project (Alt-F7) or Project >
(PrjName) Properties
Select the Toolchain menu from the left side:
AVR/GNU C Compiler > Optimization
For Optimization Level, set to None (-O0)
Please see the following link.
https://www.microchip.com/webdoc/GUID-ECD8A826-B1DA-44FC-BE0B-5A53418A47BD/index.html?GUID-9241847D-2474-41F8-86D0-BD8BCD80BC8E
Under the Toolchain settings of the current project you can select the optimization via a simple drop-down list.
Is it possible - only compile/make source in C++ Builder (XE7) without the long delay of linking?
If yes, is there a shortcut key for it?
It would be very useful when I just want to check if my code compiles at a point, but don't want to execute it.
mauroaraujo is right - since BCB4 or thereabouts the Project menu has an item that is misleadingly labelled 'Build ' + current source file. This compiles the current .cpp file (compiler switch -c). The item description in the documentation is a bit misleading as well.
The standard keyboard shortcut is Alt+F9 - the same as it always has been ever since the times of Turbo C/C++ (with the possible exception of some early C++Builder incarnations). The shortcut might change or disappear when certain editor key mappings are selected, though.
There seems to be no direct equivalent to 'Syntax check' item that becomes available in the Project menu when the current source is a .pas file, but for most practical purposes it should be close enough.
What the IDE doesn't seem to have is a command for compiling all sources without linking (sort of like a 'syntax check all sources'). However, you may be able to build a custom target where the link phase is configured to do nothing.
I read about the Runtime Sanitization in the Apple docs in the new Xcode 7, so I looked for it, and found that it's disabled. I'm using Xcode 7 GM seed.
When I go into the Run action of the scheme > Diagnostics tab, the Enable Address Sanitizer option is disabled:
There is some explanation about how other options are disbled, but no mention of why the sanitization option would be disabled:
Some diagnostic tools can be used in combination with others; the options available on the Diagnostics pane are enabled and disabled as different options are chosen to help you select option combinations. For example, enable the address sanitizer and other, incompatible tools are disabled and cannot be chosen
Looking at the Clang 3.8 documentation for Addresssanitizer, it looks like it can also be enabled, by adding a flag: -fsanitize=address. But where this flag should be used in the build settings is a mystery, and questionable since it also exists as a checkbox option in the scheme.
Also found this SO answer, but it is rather complex, and probably outdated, since it was back in 2013.
You can't currently use Guard Malloc and Address Sanitizer together. Selecting the Enable Guard Malloc checkbox disables the Enable Address Sanitizer checkbox. Deselect the Enable Guard Malloc checkbox if you want to use Address Sanitizer.
You also need to be sure you have a Mac/iOS/TV simulator selected, not a device. Watch simulator is not supported. (As of Xcode 9)
I just started playing with Dart in Dart Editor.
Since Dart Editor is a distribution of Eclipse, I figured that to format my code, all I'd need to do is press crtl + shift + f. However, when I did this, it brought up the "find/replace" window instead. I tried seeing if there were any options in "preferences" to fix this, but I found none. (The preferences seem a bit bare-bones at this point.)
So, is there a short-cut key for formatting code? And if there is, why is it not crtl + shift + f like it is in other distributions of Eclipse?
Update:
With Dart 1.2, released 2/26, you can format code through the Source menu, although the source menu doesn't exist in some situations and I'm not sure why. You can also use the shortcut Ctrl + Shift + R by default. To modify what the short cut is, you can go to Tools --> Preferences --> Key Bindings --> Export to File. Then search in the file for "Format" and modify the correct key binding, then reimport it.
Old answer:
The autoformat function for Dart code in the Dart Editor has not been introduced yet. From what I've read in the Dart formatter issue on the Dart issue tracker, it sounds like it should be introduced in version 1.2 of the Dart Editor, which hopefully won't be too long from now.
I actually did see it and use it for a few days (I think they rolled back 1.2), but there was still no keyboard shortcut for it. It was an option you needed to manually click. (Hopefully you can bind it yourself to a shortcut.)
The debugger steps into the source code on errors (like with F7), but I want to restore the normal working mode where the Delphi basic DCUs (the library) are only compiled into my code, and the sources are not used in debugging.
For example, on an error in my program, the debugger is stepping into Controls.pas, into TControl.Click. The normal case (right after installation) is for Delphi to step over these methods.
Should I recompile Controls.pas without debug information? If so, how?
I extending this theme with additional information to better understanding:
We use Delphi6 Prof. what have problem with Mouse (System Error Code 5).
So we want to recompile to Controls.pas to replace the Mouse Position getter code.
Then:
I created a folder for it: "c:\D\Common\Delphi_Patches\Delphi_6\"
I put the original Controls.pas into it.
I modified the Controls.pas, replaced the position getter code.
I set the Delphi's Library path, set the first folder to "c:\D\Common\Delphi_Patches\Delphi_6\"
With these steps I can compiled the source with mouse-safe code.
Ok, but then the Delphi everytime steps into Controls.pas on F7, and on any exceptions - this is very "angermaker" thing.
No matter that I removed the "Controls.pas" from the Library path - then the debugger is finding the original "Controls.pas" for it, and opens it... :-(
We don't use "Use Debug DCU-s" in any codes.
I tried to remove "Debug Information" from compiler options, but it is no matter, the Delphi is opens the original Controls.pas...
So I search the way to Delphi don't step into "Controls.pas", but use my dcu...
I hope this provide better context to understand the problem.
I think that you need to Shift+Ctrl+F11 (tools/options) then in Compiler, uncheck "Use debug DCU"...Then if an exception occurs it wont break into the RTL or VCL sources.
Since you are compiling your own version of a Delphi unit, you can disable debug info in that unit. Add {$D-} to the source code of the unit(s) in question.
As I see the solution is:
create a project the uses only the new Controls.pas.
unset the "Debug information" option in compiler options.
build dcu
put the dcu into a library folder
hide the new Controls.pas from this library folders.
Wite this trick the I cannot "step into" controls.pas.
Regards: dd
I had this same problem with Delphi XE8.
You can untick the "Project >> Option >> Compiling >> Use debug .dcus" and it will continue tracing into System unit and so on.
I found that the best way to stop this is to open your Application.dproj file - which is in XML. In it, you can change the settings as follows:
<PropertyGroup Condition="'$(Cfg_1_Win32)'!=''">
<DCC_AssertionsAtRuntime>false</DCC_AssertionsAtRuntime> <--- note false
<DCC_DebugDCUs>false</DCC_DebugDCUs>
<VerInfo_Locale>1033</VerInfo_Locale>
<VerInfo_IncludeVerInfo>true</VerInfo_IncludeVerInfo>
<DCC_RemoteDebug>false</DCC_RemoteDebug>
</PropertyGroup>