Scripts vs Functions

Analogy categoryAnalogies

What Is a Script?

A MATLAB script is simply a .m file containing a sequence of commands executed in order, exactly as if you typed them one by one at the command prompt. Scripts don't take input arguments or return output arguments, and every variable they create is written directly into the base workspace — the same workspace visible in the Workspace panel after the script finishes running.

🏏

Cricket analogy: a script matchDayAnalysis.m runs top to bottom like a scorer's running tally sheet, and every variable it creates like totalRuns lands directly in the base workspace visible afterward

What Is a Function?

A function begins with the function keyword and declares explicit input and output arguments. Every function call gets its own private workspace, completely isolated from the base workspace and from every other function's workspace. This means variables inside a function never accidentally overwrite same-named variables elsewhere, and data can only cross the boundary through the declared inputs and outputs.

🏏

Cricket analogy: a function computeAverage(runs, dismissals) has its own private workspace, so a local variable named total inside it never collides with a total sitting in the base workspace, unlike a scorer's shared tally sheet

matlab

% Script: raceDaySummary.m (shares base workspace)
splits = [61.2 60.8 62.1 59.9];
bestSplit = min(splits);   % bestSplit now sits in base workspace

% Function: runPace.m (isolated workspace)
function pace = runPace(distanceKm, timeMin)
    speed = distanceKm / (timeMin/60);   % 'speed' is local to this function
    pace = 60 / speed;                    % min per km
end

When to Use a Script vs a Function

Scripts suit exploratory, one-off analysis: quickly loading data, plotting it, and inspecting intermediate variables interactively is exactly what the shared base workspace is good for. Functions suit reusable, testable logic: anything you'll call repeatedly, with different inputs, from multiple places, or that you want to unit-test in isolation, belongs in a function so its behavior is predictable and its internal variables can't leak or collide.

🏏

Cricket analogy: a quick script exploring one match's data works like a scorer jotting notes during a single game, but a reusable strikeRate function belongs in every team's analytics toolkit across seasons

A good rule of thumb: if you find yourself copy-pasting the same block of script code into a second .m file with only the input values changed, that block should be extracted into a function instead.

Converting a Script into a Function

To convert a script into a function, wrap its logic in a function signature declaring the inputs it depends on and the outputs it produces, then replace hard-coded values with those input parameters. Since R2016b, MATLAB also allows local functions inside plain script files (placed after all script commands), which is a lighter-weight way to organize helper logic without fully converting the whole file into a function file.

🏏

Cricket analogy: converting matchDayAnalysis.m into function stats = matchDayAnalysis(scorecard) wraps the loose script logic into reusable form, and since R2016b you can even add a local helper like oversToBalls at the bottom of a plain script file

Once a script file's first executable line is a function definition, MATLAB treats the whole file as a function file, and the file must be invoked by calling that function — you can no longer run it top-to-bottom as a plain script and inspect leftover variables in the base workspace.

A script executes a sequence of commands and shares the base workspace with the command line.
A function declares explicit inputs/outputs and runs in its own isolated workspace.
Use scripts for exploratory, one-off analysis and functions for reusable, testable logic.
Functions prevent variable name collisions because their workspace is never shared automatically.
Converting a script to a function means wrapping the logic in a function signature and parameterizing hard-coded values.
Since R2016b, script files can contain local helper functions placed after all script commands.
A file becomes a function file, not a script, once it starts with a function definition.