Occasionally using emojis in identifiers when it is helpful - Printable Version +- QB64 Phoenix Edition (https://staging.qb64phoenix.com) +-- Forum: QB64 Rising (https://staging.qb64phoenix.com/forumdisplay.php?fid=1) +--- Forum: QBJS, BAM, and Other BASICs (https://staging.qb64phoenix.com/forumdisplay.php?fid=50) +--- Thread: Occasionally using emojis in identifiers when it is helpful (/showthread.php?tid=1622) Pages:
1
2
|
RE: Occasionally using emojis in identifiers when it is helpful - TerryRitchie - 04-17-2023 (04-17-2023, 07:16 PM)CharlieJV Wrote:(04-17-2023, 06:13 PM)TerryRitchie Wrote: Calm down Charlie. I never meant to slight you or anyone with a disability. Your original post was not clear to me as to its intent. I have Autism, my son does too, I have another son with cerebral palsy and yet another with Downs Syndrome. I understand disability, believe me. Having autism I tend to resist major change and seeing a suggestion about placing pictorials in source code pushed by "oh no" button, that''s all. Well I am truly sorry you are not going to participate because of a few dumb words I typed. Don't let my ignorance spoil your time here. Again, I'm truly sorry. RE: Occasionally using emojis in identifiers when it is helpful - SMcNeill - 04-23-2023 (04-17-2023, 01:50 AM)TerryRitchie Wrote: Let's hope that never gets incorporated into QB64. I can't stand them in text messages. In my code? No thank you. Unless someone wants to sit and do a complete rewrite of our IDE, it's just not possible. QB64PE's IDE is written in SCREEN 0, so we only have the 256 ASCII characters available with it -- which is why folks have to set the Code Page to their region, if they want accented characters and such on the screen. Our PRINT statements don't work with UNICODE characters, without mapping them to ASCII codes first, so this is something that anyone will ever see in the IDE anytime soon, just from a technical language limitation. RE: Occasionally using emojis in identifiers when it is helpful - mnrvovrfc - 04-28-2023 (04-17-2023, 12:51 PM)CharlieJV Wrote: The only thing BASIC Anywhere Machine in any of this: it allows me to try things out and see how it helps me. From now on I'm only going to comment on a feature of your project if it interests me. I'm going to reply to a post on this forum usually about QBJS if it interests me or if I have to point out a mistake, and otherwise keep away unless Pete comes back because otherwise we have no "determined" subforum moderator. Because I don't like some of your replies. I was trying to find some midway between "see how it helps me" and how it could help somebody else in this forum remotely interested in programming in a dialect of BASIC. You're adding stuff to your dialect of BASIC which is great, many things are interesting but it puts off people who don't need it, would rather run something very close to M$'s implementation. Even if it's inefficient and they have to reinvent the wheel. Even if it stays with that bug after compiling it 50 times like it often happens to me because I need a "professional" debugger at least as good as the QuickBASIC one. I should stop creating a program which is a single line of 500 lines of code, but the alternative is to use $INCLUDE files which is somewhat clunky, or wait until QB64PE gets something like support for the MAK files that didn't work with "nmake" MS-DOS utility. Keep adding stuff without caring what other people think, just like you've replied. But honestly I'm better off without anything that could run only from a web browser, or which has commands and functions that I didn't add. Sorry for sounding rude. I was holding this back for a long time because I was trying to encourage you with your project. What about the new people that signed up these past few months? That's why when posting on a forum, one has to choose what words to use. I'm not the wisest right now about choosing them... Charlie, you were the one who gave me the welcome to this forum last July. "Howdy!" I still remember that. |