News for hackers. Stuff that matters.
Re:Free Pascal by rzzzt on Sunday December 13, 2020 @12:30PM (#25408239)
For "out" variables, you can increase the indirection and pass a char** (pointer to a pointer) to the method as the argument.

Then the pointed-at pointer can be manipulated within the method body and changes will be visible on the outside as well, giving you both the numeric return value as well as the shortened string as the output. This is what the second argument of the strto{d,f,ld} function does: https://devdocs.io/c/string/byte/strtof

Re:Free Pascal by benibela on Sunday December 13, 2020 @04:13PM (#25410335)
However, such pointers are unsafe, since someone could pass an invalid or null pointer

var/out variables are much safer, since the variable exists at the calling site , is valid and not null.

It is also much safer than C++'s & references. It is very subtle, but rather amazing if you think about it. Because C++ can return a & reference, it can return a reference to a value on the stack frame of the callee, which then becomes invalid. But the var/out variable always exists on caller's site, so it is always safe.

(at least if it a reference to the stack. a reference to the heap could be freed indirectly through another reference. )

Re:Free Pascal by rzzzt on Sunday December 13, 2020 @05:06PM (#25410833)
I am not a heavyweight C++ user (also a very lightweight C and a, uhm... featherweight Pascal user), but I'd think using a C++ reference as a method argument should be as safe as Pascal's var parameters.

Is returning references frequently done in C++? I have only seen it in ostream's << operator-like constructs where you want to chain multiple calls to the same object.

Re:Free Pascal by pjmlp on Sunday December 13, 2020 @07:02PM (#25411805)
Not necessarily, although it is seldom seen I the wild, you can cast a null pointer into a reference.

Another source of issues might be the creation of temporaries.

Yes, in index operator as well.

Re:Free Pascal by benibela on Monday December 14, 2020 @06:28PM (#25424829)
>Is returning references frequently done in C++?

It is rather common to avoid copying returned objects. (perhaps it becomes less common with std::move ?)

For example, the [] operator on the standard collections returns a reference, so the item can be modified

There Pascal has another clever idea. You can overload [] for reading and writing separately. Then x[k] := v becomes x.setItem(k, v)

Re:Free Pascal by mikewarot on Sunday December 13, 2020 @12:51PM (#25408430)
I appreciate that in C pointers are the coin of the realm, I really do appreciate not having to deal all the time, stuff just works.

[Edit] For example, you can also insert into a string, making it longer, without having to worry about it.