Jump to content

Nate.N

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

8 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Great to hear that! I will continue to develop it then if it's of some use to others.
  2. I didn't see much interest in the project so I sort of shelved it, and as it relies on NodeJS to transpile, I guess it's not ideal for most people. I've had a lot of experience building transpilers and I could definitely rebuild it to work natively, including the inline ASM, but I'm afraid I don't have a lot of time right now. If I get some time soon, I can get back on it.
  3. @Lorin Millsap @Cyber https://github.com/natenorrish/enhanced-basic-transpiler This is a true BASIC parser. I've updated it to create a PRG file now instead of outputting text BASIC. I'm working on an experimental inline assembly feature, so you can code in BASIC but take advantage of machine language.
  4. I've actually developed a proper transpiler (tokenzing, parsing, etc.) which converts Qbasic to Javascript to run in the browser: So I could modify it to convert to BASIC instead, but wanted to build a quick script in the meantime.
  5. Thanks for that! I've left comments on each, and I'll take a look at the variable name issue.
  6. awesome! my next step is to implement an include statement, like you said, for multiple files. Perhaps a C style #define directive could be good to reduce variable usage.
  7. Me too, I hadn't touched BASIC for a long time, and had tonnes more experience with Qbasic, so thought I'd make it easier. The script is available here: https://github.com/natenorrish/x16-enhanced-basic-transpiler You'll need NodeJS to run it. Just a thought on the variable names, there are some rules about not being able to use keywords inside them, like: BTNCOLOR - has COLOR in it, so BASIC will throw an error.
  8. OK cool, I'll clean it up and put it on github. The exported variables could be the 2 unique letters followed by the original name?
  9. QB45 is Quickbasic 4.5 - even allows you to compile EXE files, I think QB 1.0 or 1.1 came with MSDOS as standard.
  10. UPDATE: This is now available on GitHub: https://github.com/natenorrish/enhanced-basic-transpiler I've recoded the script completely to parse and output as a tokenized PRG. I'm also planning to add inline ASM directives to use BASIC, but enabling the option to optimize parts of the program - this will be an experimental feature ------------------------------ Hey all, My retro programming background is more Qbasic than BASIC, so for me getting used to the first 2 characters only being used for variables was quite painful for me. I'm also not a fan of using line numbers, and would prefer to use subroutines as with Qbasic. I created a script (which I'll no doubt continue to develop) which converts Qbasic style code into BASIC with line numbers (please see screenshots) The BASIC output isn't pretty, and I may work on that at some stage. Features: @LABEL: Create labels using @LABEL: - this will be automatically converted to a line number, and anywhere in the code that references @LABEL will be converted to the line number Variable names: can use alphanumeric characters with underscore (I know not valid in Qbasic). Script will convert variable names to a unique 2 letter variable. This eliminates the worry of having to chose your variable names. Line numbers: automatically added in and whitspaces / blank lines are removed Comments: Qbasic style comments with single quote ' Planning to add in sub routines which auto handle variables. Anyone interested? Nate Commander X16 2020-10-06 17-12-21.mp4
  11. Hi Matej, I've sent you a PM. I think I may be able to help out. I've actually been looking for someone with knowledge on creating chiptunes, as I have an interesting project I've been working on, but I'm not a chipmusician. Cheers, Nate
×
×
  • Create New...

Important Information

Please review our Terms of Use