overview for best_username

C’est une bonne nouvelle. Il ne faudrait pas que tous les pauvres se paient une nouvelle voiture d’un coup, ça casserait le budget sans les taxes sur le pétrole. Merci Ursula.

Are memes allowed in here? by best_username_ever in c/[email protected]

[-] best_username_ever 12 points 3 days ago

No thanks.

Rapper BG ordered to have all future songs approved by US government by best_username_ever in c/[email protected]

[-] best_username_ever 6 points 4 days ago

It doesn’t matter for you since you can’t read that specific article.

Cheers! by best_username_ever in c/[email protected]

[-] best_username_ever 27 points 4 days ago

A few times ago, I was drinking beer in the street in front of an American coworker. He was a bit shocked and I said "of course you can drink wherever you want, it's the land of the free!" and I loled. I thank the internet for teaching me about weird customs all around the world. The end.

23

Is there a "markup language" to describe a debugging session? (self.ask_experienced_devs)

submitted 1 month ago by best_username_ever to c/[email protected]

1 comments fedilink

cross-posted from: https://sh.itjust.works/post/19440902

I want to document my debugging sessions in a text file but I don't know if anyone did this before.

I came up with this kind of "language" that is a mix between Markdown and C++, but I still wonder if something equivalent exists already.
// When you click on the button
# [click button]
- A::f()
// - ... other method calls, don't document if you don't need to

# A::f()
// "..." for "parameters" where you don't need the details
- Stuff::g(...)
- Stuff::h(...)

// <Class> is a fake template thing to show the possible types of an object
# <SubStuffA | SubStuffB> Stuff::g(...)
- Stuff::g() {} // empty but I use v/=> for virtual call
  v/=> SubStuffA::g()
  v/=> SubStuffB::g()

# SubStuffA::g()

# SubStuffB::g()

# Stuff::h(...)
I document methods in the order of appearance in the code.

If you have any good idea about a reliable way to document a list of function calls, I'm interested!

11

Is there a "markup language" to describe a debugging session? (self.experienced_devs)

submitted 1 month ago by best_username_ever to c/[email protected]

10 comments fedilink

I want to document my debugging sessions in a text file but I don't know if anyone did this before.

I came up with this kind of "language" that is a mix between Markdown and C++, but I still wonder if something equivalent exists already.

// When you click on the button
# [click button]
- A::f()
// - ... other method calls, don't document if you don't need to

# A::f()
// "..." for "parameters" where you don't need the details
- Stuff::g(...)
- Stuff::h(...)

// <Class> is a fake template thing to show the possible types of an object
# <SubStuffA | SubStuffB> Stuff::g(...)
- Stuff::g() {} // empty but I use v/=> for virtual call
  v/=> SubStuffA::g()
  v/=> SubStuffB::g()

# SubStuffA::g()

# SubStuffB::g()

# Stuff::h(...)

I document methods in the order of appearance in the code.

If you have any good idea about a reliable way to document a list of function calls, I'm interested!