No description provided
- Total 735
- Win 269
- Mac 311
- Linux 155
|Jul 10||Jul 9||Jul 8||Jul 7||Jul 6||Jul 5||Jul 4||Jul 3||Jul 2||Jul 1||Jun 30||Jun 29||Jun 28||Jun 27||Jun 26||Jun 25||Jun 24||Jun 23||Jun 22||Jun 21||Jun 20||Jun 19||Jun 18||Jun 17||Jun 16||Jun 15||Jun 14||Jun 13||Jun 12||Jun 11||Jun 10||Jun 9||Jun 8||Jun 7||Jun 6||Jun 5||Jun 4||Jun 3||Jun 2||Jun 1||May 31||May 30||May 29||May 28||May 27|
These modifications are specific to codechef c++ programmers. May add support for other languages in future.
see codechef/codechef_c++.sublime-build. This adds a codechef specific build system to your sublime text. to use this build system for C++, use tools->build system->codechef_c++. make sure that: * You have g++ in your path. I recommend installing dev-c++ and adding C:\Dev-Cpp\bin to your path. You can also use cygwin and keep its g++ in path but I was getting “Access denied” when compiling with cygwin's g++ so I used Dev-C++. * You have an input file(txt) with the same base name as your cpp file. so if your cpp file is my.cpp then the there should be a my.txt file in the same directory * The full path to your cpp file does not have any spaces.
After setting the build system, you can just do
Ctrl+Shift+B and see the program output just below the editing area
NOTE: while compiling the
DEBUG flag will be on. So you can surround any dirty printing in
#define DEBUG ... #endif
see codechef/codechef_c++.sublime-snippet. This adds a new snippet for your cpp files.
- open a .cpp file. If you are making a new file, first save it with cpp extension.
- type codechef, you will see a suggestion kind of dropdown, press enter on that
- navigate with
shift+tabbetween the provided places. You can still move between after modifying one of them
- Write additional
#includes in the first place, if any. if not, move forward with
- Second place is for your structs and typedefs. Hopefully by the time you reach here, you have already thought of the data structure you are going to use.
- Usually codechef has number of test cases as the first line. If it isn't there in the question, Just leave it be. What you can do here is to change the name of this variable.
Next you enter the variables which will be scanned once every test case. try entering any of these and you'll understand.
int a,b,c; long long int a,b,c; long long int a, b; int c,d; long long a,b; int c,d; long long int w;
long long int. You see that for a variable name
var, a statement
sis a macro which scans numeric inputs efficiently. Won't work on float etc. For other than numeric types, it will add the
s(var)statement but you will have to change it accordingly(
ss(var)for string(char), etc. You can look these up in the code.)
If you have any other need of global variables, put them here
You can change the namespace.
If the input has number of test cases first, press
tabto move forward, otherwise change it however you want
change scanning functions appropriately
Write your computation for a single loop. This is intented to be your top level logic. You don't need to go up in the code to define auxiliary functions. First write this part and later define other functions in the next step
Define additional functions
- To print arbitrary number of variables(debugging) use
debug(a,b,c /*and any more variables comma separated*/). You don't even need to remove your
debugstatements. No printing will occur in production.
mapcan be printed easily by
cout<<v. You can even pas a
debugas one of its arguments
How to Install
to install, download the zip, extract it and copy the extracted directory to your packages directory. On windows, packages directory is at
%appdata%\Sublime Text 2\Packages. Make sure your structure looks like this:
Packages | |-SublimeCodechef | |--codechef_c++.sublime-build |--codechef_c++.sublime-snippet
Any suggestions are welcome!
Acknowledgement: partly taken from Nikhil Garg's Answer on quora