Porting code from Python 2 to Python 3 can be a daunting task. Tools like Futureize or Modernize can do most of the mechanical work for you, and Pylint can find obvious problems with code that's meant to be 2and3 compatible. You should absolutely be using these tools as they identify the lion's share of compatibility problems. Thanks to this work, it's really never been easier to port a large codebase to Python 3.
Even with these tools, however, porting code in a way that ensures identical behavior in Python 2 and Python 3 is tough. Python is a highly dynamic language and there is a huge breadth of changes between Python 2 and Python 3. Also, while we'd all love to work in code bases with 100% unit test coverage, the reality is unfortunately often very different. Given this, it's hard if not impossible for a static analysis tool t
[Rainmeter] | |
SkinPath=C:\Users\fredrickson_m\Documents\Rainmeter\Skins\ | |
Logging=1 | |
ConfigEditor=C:\Program Files (x86)\Notepad++\notepad++.exe | |
;----------------------- | |
; META | |
;----------------------- | |
; BARS | |
[Enigma\Sidebar] | |
Active=1 |
// the OOP version in C++ | |
#include <iostream> | |
// base abstract class. that is what we use as the interface | |
class Animal | |
{ | |
public: | |
Animal(char const* name): m_name(name) {} | |
// this is required to properly delete virtual classes |
http://embedded-lab.com/blog/stm32-gpio-ports-insights/
http://hertaville.com/stm32f0-gpio-tutorial-part-1.html
The libmaple libraries, on which STM32duino is based, provides access to registers by the syntax:
GPIOA->regs->REG
#!/bin/sh | |
echo "Install neovim from ppa" | |
sudo add-apt-repository -y ppa:neovim-ppa/unstable | |
sudo apt-get update | |
sudo apt-get install -y neovim | |
sudo apt install qt5-default libqt5widgets5 | |
echo "Compile and install neovim-qt" | |
git clone https://github.com/maorv/neovim-qt.git |
* root topic - TAB and S-TAB to toggle folding | |
** child topic | |
child topic text | |
*** leaf topic: | |
some text blah | |
blah | |
blah | |
*** another leaf topic: | |
# test table - TAB to cycle through columns, M-e to move point to end of cell |
Emacs packages, features, files, layers, extensions, auto-loading, require
,
provide
, use-package
… All these terms getting you confused? Let’s clear up
a few things.
Emacs files contains code that can be evaluated. When evaluated, the functions, macros and modes defined in that file become available to the current Emacs session. Henceforth, this will be termed as loading a file.
One major problem is to ensure that all the correct files are loaded, and in the