@davepl1968 The output is undefined as per the C Standard(6.2.4). Thus what is output depends on the compiler, the standard library being used, and the platform being compiled to.
In practice, this would either segfault, print garbage data, or print the message by pure chance.
introducing:
the Orca Analog Box Controller
-true neutral additive SOCD
-variable press analog switches
-one button tilt angles, two button wd angles
-two stage spring system for physical notch emulation
-micromanage angled inputs, no modifiers
Production begins early/mid 2024
🚨🚨🚨GIVEAWAY ALERT🚨🚨🚨
After months of development and testing the N64 Tactile Z mod, it's finally ready and to celebrate I'm giving away this extra ICY N64 Controller 🥶
To Enter:
✅Like
✅Retweet
✅Follow
Winner will be chosen on 5/16, open worldwide
More deets below 👇
@c_vac_car@St0wy @FrostSSBM @imESAM@TSM_Leffen Furthermore I find you arguing against attributing open source code to their authors as disgusting and immoral.
@c_vac_car@St0wy @FrostSSBM @imESAM@TSM_Leffen An example of that copyright notice from the creators of the GPL3 license shows it giving attribution, and naming the author in the given copyright notice.
https://t.co/remkLQ2Bjw
@St0wy @FrostSSBM @imESAM@TSM_Leffen They are in violation of section 4 and 5 of the GPL. You can see more information on the thread with Frost, but them again making license violations, and failing to give attribution to the work of other developers they borrow from is greatly upsetting.
@FrostSSBM @imESAM@TSM_Leffen https://t.co/Eu7PDfzF1Q
This section of the GPL3 discusses copyright notices for verbatim source code, section 5 touches on modified source code.
https://t.co/spul7VWDCv has examples of how to make the copyright notice/attribution
https://t.co/remkLQ23tY
@St0wy @FrostSSBM @imESAM@TSM_Leffen The GPL3 isn't just a piece of text you slap on code to force everyone to opensource it, as I understand through my reading of it, there are copyright notices and attribution that must be given to the original source as per the license, and Phob fails to do so.
@FrostSSBM @Personator13@imESAM@TSM_Leffen You discussed in your discord server selling Phob kits, and the possibility of going to majors with them, which would be monetizing the project.
@FrostSSBM @imESAM@TSM_Leffen If you are going to make a channel with the statement "Discussing the Boxx-Phob IP" then someone would reasonably assume you are discussing IP between the Boxx and Phob teams
@FrostSSBM @imESAM@TSM_Leffen Putting aside the fact you had Arte release a GPL3 piece of code upon your request, Your project is still in violation of the GPL3 license that his code is under.
@Personator13@imESAM@TSM_Leffen The developers themselves were both discussing monetization, and working on a vendor list of who to buy phobs from, to which only a few people they trusted would be allowed to on that list of approved sellers.
@Personator13@imESAM@TSM_Leffen The code repository was open source but the developer had attached to the license that if they were to use his code he required they credit him and not use it commercially. And people were selling phobs at this time with code derived from that project in the phob firmware.
@imESAM@TSM_Leffen They did end up fixing the original license attribution issue, I contacted them and the author of the original code and everything got sorted out, but seeing it left a sour taste in my mouth.
@imESAM@TSM_Leffen I also know they have a secret discord channel with Hax and the people from the Boxx team where they discuss what they call the Phob-Boxx IP, I don't know what's in the channel, I just know it exists, and I'm curious why an opensource project is discussing IP with anyone.