R4d is a text oriented macro prosessor made with rust.
R4d is in very early stage, so there might be lots of undetected bugs. Fast implementaiton was my priorites, thus optimization has had a least consideration for the time.
When it gets 1.0?
R4d's will reach 1.0 only when followings are resolved.
As a binary
```bash
rad inputfile.txt -o outfile.txt
rad input_file.txt
printf '...text...' | rad -o out_file.txt
printf '...text...' | rad
rad -e FileToWriteError.txt # Log error to file rad -s # Suppress error and warnings rad -S # Strict mode makes every error panicking rad -n # Always use unix newline (default is '\r\n' in windows platform) rad -p # Purge mode, print nothing if a macro doesn't exist rad -g # Always enable greedy for every macro invocation
rad test -f frozen.r4f
rad test -m frozen.r4f ```
Type -h or --help to see full options.
As a library
Cargo.toml ```toml [dependencies] rad = { version = "0.5", features = ["full"] }
**rust file**
rust
use rad::RadError;
use rad::Processor
use rad::DebugOption;
// Every option is not mendatory let processor = Processor::new() .purge(true) .greedy(true) .silent(true) .strict(true) .debug(Some(vec![DebugOption::Lines])) // Print line by line .customrules(Some(vec![pathbuf])) // Read from frozen rule files .writetofile(Some(pathbuf))? // default is stdout .errortofile(Some(pathbuf))? // default is stderr .unixnew_line(true) // use unix new line for formatting .build(); // Create unreferenced instance
processor.fromstring(r#"$define(test=Test)"#); processor.fromstdin(); processor.fromfile(&path); processor.freezetofile(&path); // Create frozen file processor.printresult(); // Print out warning and errors count ```
R4d aims to be a modern alternative to m4 processor, which means