It's hard to keep track of bug reports, feature requests, and optimizations with the massive amount of posts in Axe threads. This is my attempt to compile all of them into one post in one thread. Hopefully this should make sure bug reports and good feature requests aren't lost and make it easier for Quigibo or any other coders who want to help to spend their time coming up with solutions instead of trying to find problems to solve.

If there are existing posts containing bug reports, feature requests, or optimizations that you don't see here, please try to direct me to the original post. If the post has some standing, I will add it to the list with ratings of importance and ease that I feel are appropriate. Please try not to debate much over the importance of items, the ratings I assign are just my rough opinions. Quigibo and any other coders can address items in any order they want.

Feel free to discuss any of these items either here or in their appropriate threads. I will try to merge good ideas and important points into the discussion section for each item.

---

• 12/18/11: [Axe 1.1.1]
  
  • -3 bugs
    
    • Error thrown at empty hexadecimal data brackets
    • [Unconfirmed] Compiling from archive sometimes fails
    • Issues with lowercase in getKey?
  • -3 feature requests
    
    • Reporting name of source file upon compile error
    • More meaningful compilation progress information
    • Display size of the compiled program during compiling
  • ~1 feature request
    
    • Switch statement
  • -4 optmization suggestions
    
    • Optimized general mutliplication
    • Optimized fixed-point multiplication
    • Optimized signed division and reciprocal commands
    • Peephole optimization of sbc hl,de \ ld a,h \ or l
• 12/18/11: [Axe 1.1.0]
  
  • +4 bugs
    
    • Error thrown at empty hexadecimal data brackets
    • Issues with lowercase in getKey?
    • Misdocumented EndIf and End!If
    • Duplication of commands referenced in Axioms
  • +5 feature requests
    
    • Automatic backup of included programs
    • Ability to execute programs upon compilation
    • Display size of the compiled program during compiling
    • Better sorting routines
    • Nested preprocessor conditionals
  • +5 optmization suggestions
    
    • Optimized general mutliplication
    • Optimized fixed-point multiplication
    • Optimized signed division and reciprocal commands
    • Peephole optimization of sbc hl,de \ ld a,h \ or l
    • Returning the full 32-bit result from the *^ operation
• 12/10/11: [Axe 1.1.0]
  
  • -15 bugs
    
    • operandNAME() parses NAME as a variable, not a function
    • Horizontal -(BUFF) does not properly adjust BUFF
    • High-order multiplication calls the wrong routine
    • Erroneously throwing errors for some pointer reads
    • Multiple bugs with peephole optimizer
    • Precedence issue with negating constant pointer reads
    • Occasional issue importing tilemaps
    • The Axe application doesn't disable G-T mode
    • The ? token lacks special meaning in strings
    • Address replacements fail in inline Axiom commands
    • Buff(CONST) accepts undefined constants
    • Lack of peephole optimizer control from API
    • ? and ? don't throw an error, given bad/no digits
    • Incorrect key for float{ in command list
    • CONST? as last line in source
  • -5 feature requests
    
    • Pre-processor conditionals
    • Improved handling of lowercase by getKey?
    • Arbitrary-sized sprite drawing command(s)
    • For(EXPR) loop
    • Including any external variable as data
  • ~1 feature request
    
    • Manual stack control for experienced users
  • -5 optmization suggestions
    
    • Optimized sort and reciprocal commands
    • Peephole optimization of inc hl \ dec hl
    • Optimized Bitmap() routine
    • Optimized input command
    • Optimized checksum routine

---

---

---

---

Yeah, the feature request list is a bit crowded. For requests for commands that you don't plan on adding, I'll make a separate section for Axiom requests and you can move anything you want into that section. But for everything that isn't simply a command request, instead of deleting things you don't plan on implementing, I think it would be better if it just had its importance dropped down to zero stars. If you want, you can add a short note in the discussion box explaining why it isn't a bug/why you won't implement the feature/why you won't implement the optimization. If you provide a good reason for not implementing it then I'll delete the entry altogether. Otherwise, I might follow it up with a counter-argument.

Bump to tell Quigibo that I have added some bugs, and to remind him that he should feel free to move any feature requests he doesn't plan on implementing either down to zero stars of importance or into the Axiom requests section as appropriate, possibly with explanation. Also if there are any bugs that you don't think are bugs, feel free to drop them to zero stars of importance as well, again possibly with explanation.

Also, reminding everybody to speak up if they know of old bugs/feature requests/optimization suggestions that aren't found on this list. I want this to be an exhaustive list of pretty much everything, and I might have missed some. And don't be shy with strange feature requests, because I'll also be trying to fill out the Axiom requests section soon, where many requests could go. I wasn't originally looking for feature requests that might be useful as Axioms, so I know I've missed some of those.

Darn nice list Runer112. This should hopefully reduce the amount of duplicate bug reports, even though they might still happen.

Updated for the past week of bug reports, feature requests, and optimization suggestions. Also updated for the release of Axe 1.1.1!