Joshua Thijssen • 11/7/2021

Let's talk about your privates

Read Original

This article presents a debate on using 'protected' versus 'private' visibility for class properties in PHP. The author, part of the minority favoring 'protected by default,' explains the differences, critiques the common 'private by default' approach for limiting user flexibility, and argues that protected access allows for more adaptable library design and unforeseen use cases.

0 comments
#software design #object oriented programming #php
Let's talk about your privates

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
React vs Browser APIs (Mental Model)
Jivbcoop • 3 votes
2
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 2 votes
3
Building Type-Safe Compound Components
TkDodo Dominik Dorfmeister • 2 votes
4
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes
5
Better react-hook-form Smart Form Components
Maarten Hus • 1 votes
6
Introducing RSC Explorer
Dan Abramov • 1 votes
7
The Pulse: Cloudflare’s latest outage proves dangers of global configuration changes (again)
The Pragmatic Engineer Gergely Orosz • 1 votes