DAY 027: _TRIM$
#2
It's a good thing QB64(PE) doesn't have "ANY" clause, that's darned confusing.

The "_TRIM$()" should be expanded to remove characters other than CHR$(32). I was going to propose only the control characters but that is useful pretty much to replicate "strings" console program that is usually packaged with gcc or with MinGW.

LOL before I got ahold of "strings" program I used to load EXE files into Wordpad to read a few amusing messages, such as the runtime error messages out of the old M$ C runtime library. "Virtual function call" and "This indicates a bug in your application" were among those messages. There was a program I purchased which created a log file while running. I peeked into its EXE file for all possible combinations and found a funny message. It was very unlikely to be triggered, during my use of that application unless I were rich and cared less about programming than about owning as much as possible to get along better with people found in the forum I used to belong to.

Another thing is to load "reaper.exe", which belonged to v1 or v2, into Wordpad or put it through "strings" program. Whoever tried to fabricate a license key and cursed out the program for not working properly could have found that program cursing at him/her back! Exclamation
Reply


Messages In This Thread
DAY 027: _TRIM$ - by Pete - 12-08-2022, 08:56 AM
RE: DAY 027: _TRIM$ - by mnrvovrfc - 12-08-2022, 10:11 AM
RE: DAY 027: _TRIM$ - by Dav - 12-08-2022, 04:08 PM
RE: DAY 027: _TRIM$ - by SMcNeill - 12-08-2022, 04:37 PM
RE: DAY 027: _TRIM$ - by SpriggsySpriggs - 12-08-2022, 05:32 PM
RE: DAY 027: _TRIM$ - by vince - 12-08-2022, 09:50 PM
RE: DAY 027: _TRIM$ - by Pete - 12-08-2022, 10:41 PM
RE: DAY 027: _TRIM$ - by vince - 12-08-2022, 11:24 PM
RE: DAY 027: _TRIM$ - by SMcNeill - 12-08-2022, 11:43 PM
RE: DAY 027: _TRIM$ - by Pete - 12-09-2022, 12:15 AM



Users browsing this thread: 5 Guest(s)