A methodology turned into a language. Good OOP becomes natural, not accidental.
Clprolf adds a conceptual layer on top of Java/C#/PHP: roles, contracts, and design rules are first-class keywords. You model systems with agents, worker agents, versions, and capacities, while the compiler enforces clarity.
- Safer architecture: compile-time errors prevent invalid dependencies
- Clear concurrency: intent expressed with
one_at_a_time,turn_monitor, etc. - Readable design: class roles (
agent,worker_agent,model) explain themselves
agent OrderService {
with_compat OrderRepository repo;
void checkout(Order o) { repo.save(o); }
}- In plain OOP: architecture drifts, concurrency bugs, endless onboarding.
- With Clprolf: contracts explicit, roles clear, design rules enforced.
-
Role-based classes:
agent,worker_agent,model,information,indef_obj -
Modifiers for real-world complexity:
long_action,one_at_a_time,dependent_activity -
Works two ways:
- Framework (annotations for Java, C#, PHP 8+)
- Language (compiles into pure Java)
- Large simulations & multi-agent systems
- Scientific prototypes with interacting “actors”
- Teaching OOP/design patterns with minimal overhead
👉 With Clprolf, your code doesn’t just run — it explains itself.
TALKING IN JAVA VERSUS TALKING IN CLPROLF – EXAMPLE
LEARNING THE CLASS ROLES THROUGH JAVA WRAPPERS
Interfaces in Clprolf — Complete Overview
Concurrency and Parallelism Aids in Clprolf
Insights About Clprolf — For Experienced Readers
Using Clprolf for Complex Object-Oriented Designs
Attempts of Multiple Inheritance with Interfaces in Clprolf
clprolf wrappers for Java Standard Libraries