Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Ha! Was this mid development or in release?
I’ve actually done a similar thing myself in the past at dev phase to stop compiler warnings etc. when I’m trying to force behaviour one way or the other but without having the actual Boolean hooked up. Always wrapped them in debug compiler constants though to prevent bleed into released code.
Two actual lines of code I stumbled upon...
static ArchiveAbstract ARCHIVE_TRUE = new ArchiveTrue();
static ArchiveAbstract ARCHIVE_FALSE = new ArchiveFalse();
Ok you might think, what is going on? Searching for it's usage yields exactly a single case:
if(someVar instanceof ArchiveTrue ? true : false)
So someone managed to introduce 3 new classes... instead of using a simple boolean.
(╯°□°）╯︵ ┻━┻
devrant