Conversation

Notices

1. Embed this notice
   gentoobro (gentoobro@gleasonator.com)'s status on Friday, 24-May-2024 03:29:49 JST gentoobro

   • Shranemone :shrimp_stars2:

   The main problem with this is the author decided that s1, s2, and s3 were good variable names. That happens in every language. It could use some more comments, and some of the sections are written in a somewhat old style (really? not using strndup?), but it's a perfectly normal parser algorithm that is perfectly understandable to anyone who understands basic C.

   Anyone who struggles with this code probably doesn't actually understand pointers and memory.
   
   RT: https://shrimpposter.club/objects/fd58d477-cde4-465c-acb5-23501760f329

   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Friday, 24-May-2024 03:29:47 JST iced depresso

     in reply to

     • Shranemone :shrimp_stars2:
     @gentoobro @shrimp they don't bother me per se, so long as i don't have to write them :blobcatshrug2:
     
     this isn't the 1980s the computer is powerful enough to handle API navigation so it should be.
   • Embed this notice
     gentoobro (gentoobro@gleasonator.com)'s status on Friday, 24-May-2024 03:29:48 JST gentoobro

     in reply to

     • Shranemone :shrimp_stars2:

     @shrimp Header files are a good thing. Aside from implementation details that they fulfill, the header file system allows very careful control of scope and namespacing without becoming verbose and annoying. They also have the effect of concentrating they layout of your data structures in one compact, easy to find place. Both of these things become very important when you start writing large, complicated programs.

   • Embed this notice
     Shranemone :shrimp_stars2: (shrimp@shrimpposter.club)'s status on Friday, 24-May-2024 03:29:49 JST Shranemone :shrimp_stars2:

     in reply to
     @gentoobro not visible in that particular example but counterpoint: header files
   • Embed this notice
     gentoobro (gentoobro@gleasonator.com)'s status on Friday, 24-May-2024 04:17:52 JST gentoobro

     in reply to

     • iced depresso
     • Shranemone :shrimp_stars2:

     @icedquinn @shrimp It's not a matter of power, it's a matter of control. You have include <string.h> and <math.h> because you are telling the compiler which strcmp and atan2 you are referring to.

     Now I hear you say "but who would ever refer to different ones?" Me, in my current project. I'm using my own versions in order to not link against the CRT, among other reasons. And that's the difference between C and most other languages. You can do whatever you want, not just what the language designers thought of.

     Besides, any significant project should have something like global.h with all the necessary standard includes, system or otherwise, which is included on the command line by the build system.

   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Friday, 24-May-2024 04:17:52 JST iced depresso

     in reply to

     • Shranemone :shrimp_stars2:
     @gentoobro @shrimp civilized people solved the problem you described by using modules and the compiler goes
     
     :blobcatconfounded: gosh darn i don't know which version of fabs you tried to call can you prefix it with the package name maybe
   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Friday, 24-May-2024 04:53:16 JST iced depresso

     in reply to

     • Shranemone :shrimp_stars2:
     @gentoobro @shrimp
     > You can't include just part of one or only some functions by only including "part" of the module.
     
     nim/python: from catblob import meow, yip
   • Embed this notice
     gentoobro (gentoobro@gleasonator.com)'s status on Friday, 24-May-2024 04:53:17 JST gentoobro

     in reply to

     • iced depresso
     • Shranemone :shrimp_stars2:

     @icedquinn @shrimp The constant.module.prefixing() seen in other languages is grotesque::and::unnecessary::visual::bloat().

     C++ is sane-ish with "using namespace foo;", though few seem to use it. You can use "import * from foo" in some other languages too, but at that point you have the same annoyance as a header file, without the ability to reasonably control it at compile time with pre-declared macros, nor the ability to usefully *-import two modules with conflicting names, which they will have because people assume::you're::prefixing::everything so it's perfectly reasonable to make a top-level.function.called.copy() in every other module.

     Another big problem with "modules" as a concept is that they aren't very flexible. They're monolithic. Either you break things apart into different modules, or they share namespaces, or you manually cherry-pick things. Into every file. You can't include just part of one or only some functions by only including "part" of the module. Headers merely inform the compiler about which functions and structs and global variable will be available from somewhere else so don't worry about it just compile this code and leave the rest to the linker. You can mix and match this however you want.

     Remember, #include is part of the preprocessor, something which very few modern languages have. Headers also sequentially bring along their macros, which are extremely powerful.