home.social

Search

59 results for “znurre”

  1. If anyone is interested in what a simple game looks like in , the source code is already available at github.com/Znurre/ld54/blob/ma

  2. If anyone is interested in what a simple game looks like in #fluenc, the source code is already available at github.com/Znurre/ld54/blob/ma

  3. Veckans Kodsnack är här: @znurre berättar om sitt programmeringsspråk Fluenc, och om faktorer för att trivas på jobbet.

    kodsnack.se/685/
    #podcast #esotericLanguages #motivation

  4. Koda utan stack … och utan dynamisk allokering
    @znurre om Fluenc, ett språk med en del ovanliga egenskaper.

    Ett utdrag ur Kodsnack 685 - lyssna där poddar finns eller på kodsnack.se
    #pocast #esotericLanguages #fluenc #znurre

  5. Koda utan stack … och utan dynamisk allokering
    @znurre om Fluenc, ett språk med en del ovanliga egenskaper.

    Ett utdrag ur Kodsnack 685 - lyssna där poddar finns eller på kodsnack.se
    #pocast #esotericLanguages #fluenc #znurre

  6. Koda utan stack … och utan dynamisk allokering
    @znurre om Fluenc, ett språk med en del ovanliga egenskaper.

    Ett utdrag ur Kodsnack 685 - lyssna där poddar finns eller på kodsnack.se
    #pocast #esotericLanguages #fluenc #znurre

  7. Making good progress on the language server this weekend!

    The idea is to later split the parts of the project into its own separate project.

    My hope is that this will make it easier for others to quickly get a C++ based language server up and running with just a few lines of code.

  8. Making good progress on the #fluenc language server this weekend!

    The idea is to later split the #lsp parts of the project into its own separate project.

    My hope is that this will make it easier for others to quickly get a C++ based language server up and running with just a few lines of code.

  9. Making good progress on the #fluenc language server this weekend!

    The idea is to later split the #lsp parts of the project into its own separate project.

    My hope is that this will make it easier for others to quickly get a C++ based language server up and running with just a few lines of code.

  10. Time for another .

    Most likely gonna try making another entry using my own language, .

    I remember doing it for LD51, and it was very useful for bringing about improvements to the language and the compiler.

  11. Time for another #ldjam.

    Most likely gonna try making another entry using my own language, #fluenc.

    I remember doing it for LD51, and it was very useful for bringing about improvements to the language and the compiler.

  12. Time for another #ldjam.

    Most likely gonna try making another entry using my own language, #fluenc.

    I remember doing it for LD51, and it was very useful for bringing about improvements to the language and the compiler.

  13. I know I've been kind of silent lately, and truth to be told, work has been the center of my attention.

    But every now and then, I work on fluenc, and the main thing that has been brewing is a language server for the language!

    Getting navigation working in an IDE/editor feels like such a huge step, and makes the language feel so much more complete in one single sweep.

    Still a long way to go, obviously, but very happy about the progress!

  14. I know I've been kind of silent lately, and truth to be told, work has been the center of my attention.

    But every now and then, I work on fluenc, and the main thing that has been brewing is a language server for the language!

    Getting navigation working in an IDE/editor feels like such a huge step, and makes the language feel so much more complete in one single sweep.

    Still a long way to go, obviously, but very happy about the progress!

    #fluenc

  15. I know I've been kind of silent lately, and truth to be told, work has been the center of my attention.

    But every now and then, I work on fluenc, and the main thing that has been brewing is a language server for the language!

    Getting navigation working in an IDE/editor feels like such a huge step, and makes the language feel so much more complete in one single sweep.

    Still a long way to go, obviously, but very happy about the progress!

    #fluenc

  16. I find that improvements to the compiler usually comes in waves.

    I have a goal in mind - a project that I am working on, and which is shaping all development of . Most new features, are added to satisfy a requirement of this project.

    Once the feature is in place and works, I can move the project further along, and often I either find bugs or performance issues that need to be fixed.

    Right now I am in the performance phase, with multiple optimizations in the pipeline!

  17. I find that improvements to the #fluenc compiler usually comes in waves.

    I have a goal in mind - a project that I am working on, and which is shaping all development of #fluenc. Most new features, are added to satisfy a requirement of this project.

    Once the feature is in place and works, I can move the project further along, and often I either find bugs or performance issues that need to be fixed.

    Right now I am in the performance phase, with multiple optimizations in the pipeline!

  18. So, one cool thing that I have been working on, is modules support. There is now a rudimentary package manager (think Cargo).

    With that in place, it felt like a great opportunity to start working on a basic standard library for the language.

    Today I added basic I/O support with streams, and very basic string formatting capabilities.

    As with most things in , it is free from runtime allocations.

  19. So, one cool thing that I have been working on, is modules support. There is now a rudimentary package manager (think Cargo).

    With that in place, it felt like a great opportunity to start working on a basic standard library for the language.

    Today I added basic I/O support with streams, and very basic string formatting capabilities.

    As with most things in #fluenc, it is free from runtime allocations.

  20. Also yes, I know I have been very silent for a while. But in my case, that just means that I am busy working on stuff.

    I have some cool progress to share with you all soon! 😀

  21. Also yes, I know I have been very silent for a while. But in my case, that just means that I am busy working on stuff.

    I have some cool #fluenc progress to share with you all soon! 😀

  22. Progress being made on Windows support. This is a screenshot showing the first ever compiled binary on Windows.

    Still some way to go though. If anyone has in-depth experience with or on , and especially , and would like to help me by brainstorming some things related to linking and deployment of executables... please let me know!

  23. Progress being made on Windows support. This is a screenshot showing the first ever #fluenc compiled binary on Windows.

    Still some way to go though. If anyone has in-depth experience with #c or #cpp on #windows, and especially #msvcrt, and would like to help me by brainstorming some things related to linking and deployment of executables... please let me know!

  24. Progress being made on Windows support. This is a screenshot showing the first ever #fluenc compiled binary on Windows.

    Still some way to go though. If anyone has in-depth experience with #c or #cpp on #windows, and especially #msvcrt, and would like to help me by brainstorming some things related to linking and deployment of executables... please let me know!

  25. Progress being made on Windows support. This is a screenshot showing the first ever #fluenc compiled binary on Windows.

    Still some way to go though. If anyone has in-depth experience with #c or #cpp on #windows, and especially #msvcrt, and would like to help me by brainstorming some things related to linking and deployment of executables... please let me know!

  26. Progress being made on Windows support. This is a screenshot showing the first ever #fluenc compiled binary on Windows.

    Still some way to go though. If anyone has in-depth experience with #c or #cpp on #windows, and especially #msvcrt, and would like to help me by brainstorming some things related to linking and deployment of executables... please let me know!