News for hackers. Stuff that matters.
Re:Codem Ipsum: Lorem Ipsum but for Code by BerislavLopac on Friday November 15, 2019 @08:29AM (#21544569)
Why code in faux Latin when you can use the real thing: http://users.monash.edu/~damian/papers/HTML/Perligata.html
Re:Codem Ipsum: Lorem Ipsum but for Code by airstrike on Friday November 15, 2019 @10:53AM (#21545793)
This is clearly the work of both a madman and a genius
Re:Codem Ipsum: Lorem Ipsum but for Code by ClumsyPilot on Friday November 15, 2019 @10:19AM (#21545496)
This is so cool! I love it.

I am a Russian speaker, and this ambiguous aspect of English has always bugged me to hell! I think english was a bad model as a starting point for programming languages.

Re:Codem Ipsum: Lorem Ipsum but for Code by Aloha on Friday November 15, 2019 @11:12AM (#21545998)
How so?
Re:Codem Ipsum: Lorem Ipsum but for Code by SamBam on Friday November 15, 2019 @11:29AM (#21546180)
I'm guessing they're referring to linguistic features that English doesn't have, such as inflected nouns to unambiguously indicate the subject, direct object and indirect objects.

`bite(dog, man)` is ambiguous. You need to look up the function documentation, make a guess, or ask the library developer to come up with a less ambiguous name.

If you could decline your variables, however, you could write (in terrible fake Latin)

`bite(dog, man-um)` or `bite(dog-um, man)` and they would be interpreted as two different -- and unambiguous -- things.

...but I'm just repeating GP's article.

Re:Codem Ipsum: Lorem Ipsum but for Code by zamubafoo on Friday November 15, 2019 @11:53AM (#21546402)
It might just be me, but isn't that just how you name your attributes within the function definition? I don't see how that would help disambiguate without have to look at the function definition at the very least.
Re:Codem Ipsum: Lorem Ipsum but for Code by SamBam on Friday November 15, 2019 @02:11PM (#21547763)
The point is it's a new way of looking at arguments (in this toy example). In Latin, the order of the nouns typically does not matter. Their role in the statement is unambiguously determined by their declension.

So if you wrote a library with the verb "bite", you wouldn't specify that the first bites the second, or the first was bitten by the second. Those are ambiguous, because they're you're choice as a developer. Rather, you'd specify that the noun in the subject case bites the noun in the object case. That's unambigious in all declined languages.

So, as a reader of someone else's code, I can see immediately that `bite(boy-um, dog)` -- in my fake Latin where "um" denotes the object (cf. "Puer - Puerum") -- that the boy was bitten by the dog. I don't need to look up any documentation or look at how the variables are named in a third-party library.

Again, of course this case is a toy example. The article is more in-depth.

Re:Codem Ipsum: Lorem Ipsum but for Code by tuesdayrain on Friday November 15, 2019 @05:28PM (#21549418)
`bite({from:Dog,to:Man})` solves the ambiguity in my opinion.
Re:Codem Ipsum: Lorem Ipsum but for Code by meddlepal on Friday November 15, 2019 @11:36AM (#21546249)
I just proposed my team switch to this haha, awesome.
Re:Codem Ipsum: Lorem Ipsum but for Code by jacobush on Friday November 15, 2019 @09:12AM (#21544895)
I didn't expect it, but I thought Perligata is more readable than Perl.
Re:Codem Ipsum: Lorem Ipsum but for Code by skykooler on Friday November 15, 2019 @10:10AM (#21545392)
At least, apart from numbers, which all are rendered in Roman numerals.
Re:Codem Ipsum: Lorem Ipsum but for Code by libeclipse on Friday November 15, 2019 @09:22AM (#21544986)
Not a difficult task lol