What are some pros and cons of a scope keyword? (lemmy.basedcount.com)

submitted 8 months ago by librecat@lemmy.basedcount.com to c/programming_languages@programming.dev

7 comments fedilink hide all child comments

In something like C++ you could create a scope like so:

{
	// Do something neat here
}

I was wondering about having or maybe even requiring a scope keyword, which might look like this:

scope
{
	// Do something neat here
}

This seems even more relevant in an indentation sensitive language like python:

scope:
	pass

Interested to hear any opinions, TIA.

you are viewing a single comment's thread
view the rest of the comments

[-] Kissaki@programming.dev 2 points 8 months ago

What's the intention and use case for this?

Only for empty, unlabeled, untyped scopes? Or would I write

function a() scope {}

Is it necessary for scope-ending cleanup of resources? If so, I would consider whether there are not better solutions for those.

Is it for code structuring? I would also consider what use a scope keyword has then, and what the alternatives are.

I don't see how adding a scope label helps with anything.

[-] librecat@lemmy.basedcount.com 1 points 8 months ago

To be honest, the only use case I really thought of was something like unlocking a mutex at the end of a scope or maybe a file.

[-] anton@lemmy.blahaj.zone 2 points 8 months ago* (last edited 8 months ago)

In that case managed languages like python and java combine that functionality with try blocks. This is generally called try with resources.
C# has the using keyword that just uses local scope.

The commonality between them is declaring which resource is managed, not just everything is a scope. Imagine you wanted to manage one resource and return another.

[-] librecat@lemmy.basedcount.com 1 points 8 months ago

I was just thinking about Python's with

load more comments (1 replies)

this post was submitted on 03 Mar 2024

9 points (84.6% liked)

Programming Languages

1160 readers

2 users here now

Hello!

This is the current Lemmy equivalent of https://www.reddit.com/r/ProgrammingLanguages/.

The content and rules are the same here as they are over there. Taken directly from the /r/ProgrammingLanguages overview:

This community is dedicated to the theory, design and implementation of programming languages.

Be nice to each other. Flame wars and rants are not welcomed. Please also put some effort into your post.

This isn't the right place to ask questions such as "What language should I use for X", "what language should I learn", and "what's your favorite language". Such questions should be posted in /c/learn_programming or /c/programming.

This is the right place for posts like the following:

"Check out this new language I've been working on!"
"Here's a blog post on how I implemented static type checking into this compiler"
"I want to write a compiler, where do I start?"
"How does the Java compiler work? How does it handle forward declarations/imports/targeting multiple platforms/?"
"How should I test my compiler? How are other compilers and interpreters like gcc, Java, and python tested?"
"What are the pros/cons of ?"
"Compare and contrast vs. "
"Confused about the semantics of this language"
"Proceedings from PLDI / OOPSLA / ICFP / "

See /r/ProgrammingLanguages for specific examples

Related online communities

founded 1 year ago

MODERATORS

armchair_progamer@programming.dev