Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone
  1. Home
  2. Categories
  3. Uncategorized
  4. I think this is the beginning of a beautiful #jam.

I think this is the beginning of a beautiful #jam.

Uncategorized
1 1 1
Log in to reply

Feed RSS
I think this is the beginning of a beautiful #jam.

Gli ultimi otto messaggi ricevuti dalla Federazione
@pierobosio@soc.bosio.info
Post suggeriti
  • Elena Rossini on GoToSocial ⁂undefined

    Giving #Sharkey one more try (the 9th for the record)

    Uncategorized sharkey sharkeymonamour mysocalledsudolife
    1
    0 Votes
    1 Posts
    0 Views
    Elena Rossini on GoToSocial ⁂undefined
    Giving #Sharkey one more try (the 9th for the record).Yes I can be pretty persistent, LOL 😅​Send me pictures of your cute pets in case it doesn't work... 🙃​#SharkeyMonAmour #MySoCalledSudoLife
  • Oblomovundefined

    Pane e panel

    Uncategorized giochidiparole
    1
    0 Votes
    1 Posts
    0 Views
    Oblomovundefined
    Pane e panel#giochiDiParole
  • Luca Sironiundefined

    ma in pensione non ci vuole andare nessuno ?

    Uncategorized
    4
    0 Votes
    4 Posts
    0 Views
    Comandante Virgola :snwfn:undefined
    @luca il potere, mio caro: il POTERE ... 🙄
  • Paolo Amorosoundefined

    Ned Batchelder @nedbat on why exceptions are better than returning status codes.

    Uncategorized programming
    3
    0 Votes
    3 Posts
    0 Views
    arclightundefined
    @amoroso @nedbat Exceptions are three GOTOs in a trenchcoat. :)Seriously though, it wasn't until reading Object Oriented Software Construction by Bertrand Meyer that I became comfortable with exceptions. This the book that introduces the Eiffel language and Design by Contract (DbC). It's a great book - clear and insightful, engaging and readable for a textbook - very highly recommended.Meyer's position was that you clearly define the scope of responsibility of a routine as well as its requirements and expectations. Exceptions are for exceptional conditions _only_ - issues where the routine's contract with its caller is broken. DbC makes you think more clearly and intentionally when you create a routine; part of that is clearly documenting which exceptions a routine can throw. One of my biggest complaints about OO systems is that there's no way to get a complete list of exceptions that could be emitted from a function call so you can effectively handle them; I'm not sure that's even possible. Either way it makes the code difficult to reason about. Not that status codes are any better in practice - the tradeoff seems to be between clear implementation code and routines with clearly documented behavior.As noted in the post, some languages don't have exceptions; here's an exploration into error handling in Modern Fortran that tries to do better than just returning an integer https://matthiasnoback.nl/2025/07/fortran-errors-and-error-handling-part-1-exploration/