Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Code Reviews

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on BMPL: The language I'll bring to life

Post

BMPL: The language I'll bring to life

+4
−1

Last year, I started working on a language I named SuperCode but then decided BMPL (Builder's Multi-Purpose Language) as the final name. The language would be written using C and up until now, the GitHub repo only consists of a library of functions.

I decided to bring up the language onto Codidact's chat and have even started using it as some programming language, where I'd access the functions and assign them in TIO. To this day, I'd continue making answers on Code Golf CD using the language which is, until now, a library of libraries.

For this review, I want to know anything that can be improved with the functions and what could be fixed from what I made. I'm certain all functions I made before 2021 (all libraries except time.h and is_type.h) work properly ever since I tested them.

Here's the most commonly-used function I have:

#define say(X) printf(_Generic((X),   \
                        double: "%f", \
                        float:  "%f", \
                        char *: "%s", \
                        int:    "%d"  \
                ), (X));
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Expected library usage? (2 comments)
Expected library usage?
Lundin‭ wrote over 3 years ago

How is one expected to use this library? It is custom for library APIs to have one "super header" including all other headers of that library, so I'd expect to find some "bmpl.h" and only include that one. (Note that "super headers" is generally bad practice except for front-end to large libraries.) Some famous examples of such "super headers" are windows.h and pthread.h. I'm posting this as a comment since I'm not sure if I'm missing something here.

General Sebast1an‭ wrote over 3 years ago

Lundin‭ You can access the header files via #include "Library/something.h", something I learned when I was making the language.