ByteC v2.0: The Pocket C & C++ Survival Guide

Welcome. If your college C programming course started this week, you do not own a laptop, and the black Termux screen looks like a 1980s hacker movie, you are in the right place. ByteC turns your Android phone into a 120MB C and C++ studio with plain-English commands, an offline error tutor, and one-command PDF/DOC lab reports.

Zero-to-One: What Even Is a Terminal?

On a phone, you tap icons to open apps. A terminal (also called the command line or shell) skips the icons and lets you send text messages to the operating system. You type a command, press Enter, and the phone runs it and prints the answer back.

Why Can't My Phone Run C Code Right Away?

When you write a C program, you write human-readable text like printf("Hello\n"); inside a file named lab1.c. Your phone's processor (the CPU) does not speak English or C. The CPU understands raw binary numbers (machine code) and nothing else.

To bridge that gap, you use a compiler (ByteC uses Clang, wrapped so gcc and g++ work too). The compiler reads your lab1.c text file, checks whether you forgot any semicolons, and translates the whole thing into a binary executable that the CPU can run.

1-Click Termux Setup

Follow these four steps once. The entire installation takes about two minutes and uses 120MB of storage instead of a 5GB Ubuntu container.

termux-setup-storage

curl -sL https://raw.githubusercontent.com/0xOpCode/ByteC/main/install.sh | bash

source ~/.bashrc
bytec

The 6 Magic Words (code, run, explain, check, fix, submit)

Traditional Linux makes you memorize flags like gcc -Wall -Wextra lab1.c -o lab1 -lm && ./lab1. ByteC v2.0 gives you six single-word commands. Even better: ByteC remembers the last file you edited in ~/.bytec/.last_file, so you can run these commands without retyping the filename.

code lab1.c

run lab1.c

explain lab1.c

check lab1.c

fix lab1.c

submit lab1.c

How explain, check, and submit Save Your Grades

1. explain: The Offline Compiler & Crash Translator

Compilers were written by systems engineers for other systems engineers. When you forget a semicolon on line 9, Clang points at line 10 and complains about something unrelated. When you forget & in scanf, your program dies with Segmentation fault and tells you nothing.

explain runs 100% offline across three stages:

• Stage 1 (Static Capture): Runs Clang with strict diagnostics (-Wall -Wextra -Wformat -Wuninitialized) and extracts your source lines.
• Stage 2 (25+ Student Error Rules): Matches mistakes like missing ; on the previous line, missing & in scanf, = instead of == in if, uninitialized stack garbage, missing headers (<stdio.h>, <stdlib.h>, <math.h>, <string.h>), and removed gets() calls.
• Stage 3 (Runtime Crash Forensics): If your code compiles but crashes while running, explain decodes the crash signal (SIGSEGV Exit 139 for bad memory access, SIGFPE Exit 136 for division by zero, SIGABRT Exit 134 for double free or stack overflow) and shows the crashing line and local variable state.

[EXPLAIN] Issue found in lab1.c (Line 8, Column 18)
  8 |     scanf("%d", age);
    |                 ^~~
What happened:
  scanf needs the memory address of 'age' so it knows where to store the number.
  Passing 'age' without '&' sends its uninitialized value as a memory address,
  which triggers a Segmentation Fault crash.

How to fix (Before vs After):
  - Before: scanf("%d", age);
  + After:  scanf("%d", &age);

2. check: 4-Layer Verifier & 5-Second Infinite Loop Guard

Every C student writes a while (i < 10) loop where i never increments. In a normal terminal, the program freezes forever until you mash Ctrl+C. When you run check lab1.c, ByteC runs four verification layers:

1. Layer 1 (Static Bug Scan): Flags scanf without &, fflush(stdin), void main(), gets(), uninitialized variables, and malloc() without a matching free().
2. Layer 2 (Memory & Bounds Protection): Compiles with stack smash protection and bounds checks.
3. Layer 3 (5-Second Watchdog Timer): Runs your binary under a 5-second timeout. If your code gets stuck in an infinite loop, check halts the process after 5 seconds and tells you to inspect your loop counter.
4. Layer 4 (Multi-Case Test Suite): Pass a test file with multiple --- INPUT --- and --- EXPECTED --- blocks to grade your program before your professor does.

check lab1.c
check lab1.c tests.txt

3. submit: Instant .doc & .pdf Lab Reports in Downloads/ByteC

Formatting college practical records on a phone is painful. Running submit lab1.c automates the entire lab record workflow offline:

1. Storage Permission Guard: Checks if /sdcard/Download/ByteC is writable. If Termux does not have storage permission yet, submit launches termux-setup-storage, waits for you to tap Allow, and creates the folder.
2. One-Time Student Profile: Prompts once for your Full Name, Roll Number, and Batch, saving them in ~/.bytec/student_profile.conf for all future practicals.
3. Live Input-Echo Transcript: Runs your program and echoes every input value next to its prompt (for example, Enter number: 29) so the output box in your report reads like a real terminal session.
4. Zero-Dependency .doc + .pdf Output: Writes both lab1_LabReport.doc (Word/WPS/Google Docs compatible RTF 1.5 with bordered code boxes) and lab1_LabReport.pdf (native PDF 1.4 generated offline via POSIX awk) straight into /sdcard/Download/ByteC/ and fires an Android notification.

submit lab1.c
submit lab1.c -i input.txt

Surviving Neovim (Without Rebooting Your Phone)

There is an old computer science joke: "How do you generate a random string? Put a first-year student in Vim and ask them to exit."

People get trapped in Vim/Neovim because it has two main modes instead of one. Once you understand the difference between Normal Mode and Insert Mode, you will never get stuck again.

Complete Neovim v2.0 VS Code Shortcut Table

Upgraded 2-Row C Symbol Touch Bar

Phone keyboards hide C operators across three sub-menus. ByteC configures a 2-row hardware toolbar above your keyboard with every token required for headers, pointers, format strings, and bitwise logic:

Row 1: [ ESC  | TAB  | CTRL | ALT   | { | } | ( | ) | ; | " ]
Row 2: [ LEFT | DOWN | UP   | RIGHT | # | < | > | & | * | = ]

Swipe up or long-press on the touch bar keys to insert secondary brackets and operators ([, ], \, |, /, -, _).

The 3 Classic C Traps (Read Before Lab 1)

C gives you direct access to memory and trusts that you know what you are doing. Here are the three traps that catch every beginner in week one, and how to beat them.

int age;
scanf("%d", age);   // CRASH: Sends uninitialized value as a memory address
scanf("%d", &age);  // SAFE:  Sends the memory address of 'age'

char name[50];
scanf("%49s", name); // EXCEPTION: An array name already points to its address

if (marks = 100)    // BUG: Overwrites marks with 100, condition is always true
{
    printf("Full marks\n");
}

if (marks == 100)   // SAFE: Compares marks against 100 without changing it
{
    printf("Full marks\n");
}

int scores[5] = {10, 20, 30, 40, 50};

// BUG: Using <= 5 steps onto scores[5], which is out of bounds
for (int i = 0; i <= 5; i++) { ... }

// SAFE: Valid indices for size 5 are 0, 1, 2, 3, 4 (i < 5)
for (int i = 0; i < 5; i++)
{
    printf("%d\n", scores[i]);
}

18 Built-in Lab & DSA Templates

Start any college practical with a working, well-commented reference program using code lab.c -t <name>. Filter or search the 18 built-in templates below:

Classic CLI Tools & ByteC Studio Manager

Run bytec with no arguments to launch the interactive Studio TUI menu, or run any subcommand:

bytec                   # Launch interactive ByteC Studio TUI menu
bytec doctor            # Check compilers, storage permissions, and git setup
bytec learn             # Interactive offline C lessons and coding challenges
bytec resources         # Print curated C, C++, DSA, and Linux learning links
bytec cheatsheet printf # Offline reference (printf, pointers, strings, loops, dsa, keys)
bytec backup            # Save zip/tar backup of ~/c_projects into /sdcard/Download/
bytec update            # Update ByteC tools and Neovim configuration

Free Learning Roadmaps & Resources

Bookmark these free books, visualizers, and interactive courses. Every resource below works well on mobile browsers.

1. C Programming (Zero to Hero)

2. C++ & Data Structures / Algorithms (DSA)

3. Linux, Terminal, Git & Termux Mastery

Troubleshooting & FAQ

1. Where are my C files and lab reports saved on my phone?

Your source code lives in ~/c_projects, which links to /sdcard/C_Projects in your phone's internal storage. When you run submit lab1.c, your .doc and .pdf lab reports are saved inside /sdcard/Download/ByteC/ so you can share them on WhatsApp, Google Classroom, or email right away.

2. My touch keyboard disappeared in Termux. How do I bring it back?

Tap the center of the terminal screen. If it stays hidden, swipe the left drawer open in Termux and tap KEYBOARD, or hold Volume Up + Q to toggle the extra keys bar.

3. Why did my program print a giant random number like 32765 or -1094795586?

You declared a local variable like int sum; without setting it to 0 (int sum = 0;). Local variables in C do not start at zero; they hold whatever leftover bits were sitting in RAM before your function ran. Run explain or check and ByteC will point out the uninitialized variable.

4. How do I uninstall ByteC without losing my code?

Run bytec uninstall. It removes the CLI scripts and shell hooks while leaving all your files in ~/c_projects and /sdcard/C_Projects intact.