QB64 Phoenix Edition v3.2.0 Released!

[DSMan195276]

• I've been able to reproduce several times a blocking problem that freezes the IDE. Then, I've to kill the QB64PE process and QB64PE can't even be restarted unless you clean the /internal/temp folder. I'll give more details on another dedicated message.
  
• The new -f switch kills the original -f switch that was used to load a file in the IDE (please see the original qb64.sh (now /usr/bin/qb64pe.sh or simply run qb64pe -h) prior to create new switch.
  

Requests:

• Due to the speed of new releases, is it possible to display the release version (currently 3.2.0) into the IDE title bar?
  
• In the "Run" menu of the IDE, would it be possible to add an option "Run as" and a second option "Make executable only as" (to simulate the -o switch)?
  
• When using the -x switch, would it be possible to have a complete silent output for example by adding a -n switch (for no blabla)? Then the return codes of the compilation process could be 0 if the compilation failed and 1 if the compilation was successful?
  
• For both Linux and macOS, would it be possible to compress  the project with the .tar.bz2 option Vs the .tar.gz. There is a gain of 20 % in size. And the size matters LoL
  
• Would it be possible to have a fixed place on GitHub where should always be posted the latest QB64PE release without any numbering version such as "QB64PE_latest-lnx.tar.bz2" and "QB64PE_latest-osx.tar.bz"? This is not in contradiction of the current way but a simple request that would avoid for me to store the package on my own web sever at home since i've a low bandwith.
  
• Finally, could my installation script become the standard installation script included in the QB64PE package? If not, why?
  

In regards to the blocking issue, yes please write a clarification of it somewhere. We resolved one such issue a few months ago, I wasn't aware there was another (or that the original wasn't resolved for you).

For the `-f` switch, can you clarify, you're saying QB64-PE itself already had an `-f` switch? I just checked to be sure and the older QB64PE versions do not support an `-f` flag, the behavior you're talking about works by just passing a filename with no flag. We didn't remove an `-f` flag in QB64PE, so perhaps the flag was removed in some older version of QB64?

All your requests seem pretty reasonable  I'd ask that you make GitHub issues for them if you can, that's the best way to make sure they don't get lost. Also I would try the existing `-q` switch for quiet output, I believe it will give you what you're looking for.

In regards to your installer, it's possible but we would need to talk about it. I'm not particularly tied to the existing install script, but switching to yours would be a fairly major change in how QB64-PE installs on Linux since you place things in global directories and also provide other helper scripts and such (which is not a bad thing! but still a major change). Personally I'd rather just look at creating proper packages for the more popular distributions rather than more complicated install scripts, but I also think proper packages are a long way out so perhaps your install script could be a reasonable in-between (potentially offered along side the existing one).

All looks good from here. Please, guys, don't burn out!! These rapid updates make me nervous. We've had enough teams burning out already! 

I wouldn't worry too much about that personally Honestly the release schedule makes things easier, no reason to rush stuff if it can just go in a release next week. I also wouldn't expect new features every week, that wasn't and isn't the goal. Things get done when they get done