48 karma · joined September 16, 2017
Of course, git cloning the ALE plugin (linter + languageserver) for VIM also fails as ALE has an .odin file in its repo.
The C++ frontend of MSVC handles (the common) compiler-specific language extensions differently than the other compilers. Besides, its pre-processor behaves differently too. It is now good that there is a clang frontend for MSVC.
- GCC switched from C to C++
- CUDA switched from C to C++
But I can understand the decision, and at that time , C++ frontend features and libs were a little bit less horrible.
However, not everything can be well designed at the beginning. Skills of editing will affect efficiency, especially in a try-and-error loop of new ideas/approaches, where only a rough design exists.
Besides, some niche editing tasks (which may involve column editing, macro recording then batched execution, regex based operation, encoding transformation etc.) may otherwise require writing awk/sed or even perl/python scripts as subprojects to achieve, if one does not known the editor well.
No Markdown, no Perl/Python/Ruby, also no binary program, just a few simple shell scripts and plain HTML files.
External code generation requires (cross) execution of the (cross) compiled binary program.
As user of the modules, venv is sufficient.
I am also able to integrate (a locally hosted) LanguageTool to check the grammar in the editor.
The only issue is to write emails with embedded images. But personally I don't like such emails for occupying the space of the mailbox.
What is the reason that it appears on Nature? Just because the genetic methods become the hype (again)?
Representing the pages as big images not only takes more space to store/archive, but also increases IO-time for loading the documents.
If I remembered correctly, debug was only capable of writing 64kB (mono-segment) data? Though one can always create an in-RAM program inside debug to output larger files.
--[
]--++[ ]++