196

16891 readers

932 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

If you have any questions, feel free to contact us on our matrix channel.

founded 2 years ago

MODERATORS

335

Lua rule (lemmy.blahaj.zone)

submitted 11 months ago by Finalsolo963@lemmy.blahaj.zone to c/196@lemmy.blahaj.zone

16 comments fedilink hide all child comments

A ruler with the logo for the Lua Programming language

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

[–] ezchili@iusearchlinux.fyi 1 points 11 months ago* (last edited 11 months ago) (1 children)

Why do you assume it was a pointer type? There's no types. Why do you assume C either? This is pseudo code to illustrate pointer offsets

[–] barsoap@lemm.ee 1 points 11 months ago (1 children)

Why do you assume it was a pointer type?

Because afterwards you said arr[n]. By convention n is definitely an integer and if arr is also, say, an integer, you get

 error: subscripted value is neither array nor pointer nor vector

Why do you assume C either?

Because you didn't write ^(@arr+0) (Not sure that's even valid though my Pascal is very rusty).

This is pseudo code to illustrate pointer offsets

Granted. But then it's still Pseudo-C, not Pseudo-Pascal or Pseudo-Whitespace.

[–] ezchili@iusearchlinux.fyi 1 points 11 months ago* (last edited 11 months ago)

It's pseudo-nothing

It conveys a point, which you got, and if you decide to invent a syntax and bicker on it it's just you

Really pointless discussion