99
Why make it complicated? (lemmy.ml)
submitted 1 year ago by to c/programmerhumor@lemmy.ml
51 comments fedilink hide all child comments
 

Made with KolourPaint and screenshots from Kate (with the GitHub theme).

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 year ago (4 children)

What about you declare (then it gets allocated in stack) it and pass it to a different context for assignment?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 1 year ago* (3 children)

    Well, I don't know your use case well enough, but I guess you might have perfect reason for that behavior.

    One thing that comes to my mind is the old Try in C#

    bool parsedSuccessfully = int.TryParse("123", out int result);

    But I guess more popular approach would be to use Error as Values, right?

    E.g. something like this

    Outcome<Exception, Int> result = int.TotallyNewParse("123");
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 1 year ago (2 children) 
    char c;
scanf("%c", &c);
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    Great example.

    Wouldn't getchar() be more appropriate here? Last time I used C it was 16 years ago.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 1 year ago

    Yes, and no, sir, you missed the point. The procedure here is to allocate then give away, not reading a fixed-length returned value.

    Say you can only afford to have ten bytes in the stack. You allocate char s[10]; then give it to a library to parse something. Also telling it to abort if it's going to be longer than ten bytes, of course.

  • permalink
  • fedilink
  • source
  • parent