Wait so this is practical language development too?

As in, not just recreational languages?

I'm not sure; i was under the impression that it was just general development-related things

might make more sense to divide it up though

Currently it's general language dev

TBH all of the planned sections apply to any type of language, not just golfing languages

Question: is it okay if I base my sections on what I've learned from esolang development?

What else would you base it on?

Observations of practical languages

True

General trends among actually used languages.

As long as it's useful and somewhat broad in scope it should be fine

Problem is that I know more about golfing paradigms then actual paradigms

i know a bit about actual paradigms and maybe limited knowledge on implementation and memory management for various language types

in the meantime i'll try to find stuff for the underappreciated answers subsection

if any of you have answers you think would be good candidates please let me know

What memory model would you say a language like python uses?

Also, to be clear, are Postfix/stack/prefix/tacit/Accumulator based memory models?

i would say not really

i meant more so like memory management for the interpreter, for example, managing the stack properly for doing tail recursion to allow unbounded recursion depth

i'm not sure what i would call what you listed

i'd say postfix/infix/prefix/tacit are one thing

and stack/accumulator are another thing

but i'm not sure what i'd call them, so i can't really assert that my assessment would be accurate either :P

Hang on so we're not talking about paradigms at all?

In that case, memory models don't seem that helpful to discuss.

i don't think memory models and management are relevant to paradigms specifically. sorry, i shouldn't have brought it up now, i meant it as an addition, not that it was something to discuss with paradigms here lol

But I mean if models and pre/post/in/tacit are different, then how can considering memory models help with language development?

And what is actually meant by memory models?

uh. okay so to clarify. i'm not too familiar with memory models (as in, what one even defines as that). i learned a bit about memory management in CS146, but i do not know about memory models that much and i did not intend to communicate that i did understand :P

idk, i think like, stack-based, tape-based, tacit would count as memory models?

as in how the program itself sees its memory, not how the underlying interpreter manages that memory

I can do that

And so registers is what languages like python/java/c++ use?

I'd say the heap + the stack + the registers is more like what they use, right?

Heap - that's the word I was looking for

i'm not sure about python, lol. i'd say just heap, cuz it just sort of dumps a bunch of memory randomly into a place and can do whatever, and i guess the interpreter has to then track that and make sure to throw it out once it's done

maybe i should've just passed on signing up at all this time. i am feeling grossly underqualified compared to y'all :P would leave me with more time to organize and consider other things on meta rn anyway

I haven't started yet

My questions are to help me organise myself

@hyper-neutrino I'm almost certain you're much more qualified to talk about a lot of this stuff than me :p

^

lol. well thanks y'all for the confidence that i don't have :P

I mean I just learned about tail call optimization a week ago, and I wrote three esolangs before I learned the word "accumulator" :p

I just transpile to python

well for golfing langs / esolangs you guys probably have a bit more experience :P i've made a lot of languages but with my limited experience, they're nothing worth talking about and taught me very little

if we do talk about stuff like tail optimization and more practical stuff i might be able to write up some stuff for that :P

Correct :p

I wasn't kidding @Lyxal

I never reopened anything

*shakes head*

I'll add you back as a collaborator in a couple of days; it's disruptive to everyone who's a collaborator on the repo

I never broke the rules technically though

Yeah, I ain't arguing this

← 8 messages moved from The Nineteenth Byte