I work for a relatively major fintech company, and we have used GitHub actions at scale to automate a ton of workflows, some examples include:
- code and file validation. - unit testing. - cloud infrastructure deployment. Github Actions are just a good way to automate and glue together different things. For example, embedding your tokenizer into an action would potentially allow anyone who wants to write Tandy BASIC code and publish it to GitHub to automatically tokenize it from ASCII on commit. Alternatively if you prefer to be a bit more generic, you could put your Tokenizer behind an API and then create a Github action that basically just interfaces with that API. That way people who aren’t using Github could still access your Tokenizer-As-A-Service (TAAS) This seems like a promising solution. However, I don’t really know anything about C executables, I’m afraid I live over in Python land. -George On Tue, Feb 28, 2023 at 2:20 PM B 9 <hacke...@gmail.com> wrote: > On Mon, Feb 27, 2023 at 7:51 AM grima...@gmail.com grima...@gmail.com > <http://mailto:grima...@gmail.com> wrote: > > Currently I’m using VS Code and Virtual T in tandem to develop. It would >> be great if there were a modern tokenizer and packer written in Python or >> similar. > > Last year I wrote a tokenizer in C. ¹ > > https://github.com/hackerb9/tokenize > > It can handle WIDTH and DSKO$ and it’s easy to add new tokens if some > other variant of BASIC appears. > > While it will work fine for your project, I consider it incomplete as it > does not generate N82 BASIC tokens, yet. > > I’m curious about people’s experiences using GitHub Actions. I haven’t > used them as I worried it would tie my projects too closely to one company. > Now that Nektos' act <https://github.com/nektos/act> exists, I'm > reconsidering. > > —b9 > ------------------------------ > > ¹ Technically, I wrote it in flex which made tokenization trivial. Flex > outputs C code, so the program runs anywhere without requiring flex as a > dependency. I haven’t tried it, but there is a tool called Flex.js which is > supposed to output JavaScript, if you’re into that kind of thing. >