Now, I'm curious: if you're a Computer Scientist, can't you determine when some code is 'beginners code' (as BasicCoder2 wants to put it) ? There seem to be, some very wrong assumptions, from your end. Computer Science != Programmer (okay, some are Dev's, others are Admin's) I've for a long time do...

BasicCoder2 wrote:The context was, "unreadable to beginners".

The context is, "incomprehensible to beginners", even if perfectly "readable".

Example:
Text written in italian, prefectly "readable" but still not "comprehending", what it means ...

Anyway they would all be scared away by all the unreadable coding by the resident experts :) Please, don't use "unreadable" to mean "incomprehensible", the two words have a distinctly different meaning ... (unreadable = spaghetti code, or badly formatted code). I further think, ...

dodicat wrote:If Mr Swiss gets a degree in computer science, life will be hellish on the forum.

Sorry dodicat, got that already a long time ago, aka: nothing to worry about!

coderJeff wrote:Kind of highlights the overuse of "reference" in this concept/topic, lol.

Yes, the "level of indirection" could be a different approach, to stated dilemma. Aka:

first level = Pointer (exposed indirection)
second level = Reference (hidden indiretion/*ptr)

Maybe?!?

Hi, welcome to the forum. Integers are "whole numbers" only, if you want decimals you'll have to use floats: Single (precision) 32 bit, or Double (precision) 64 bit. See: Wikipedia for detailed info. dim as single fr, fe, ama, ima, eff, choice print "What Simple Machine do you want to...

"dereference" sounds like it is taking away a reference. Well, I tend to look at it from the pointer itself, which is dereferenced, to get/set the "value it points to" (debatable, for sure). Personally, I've only understood pointers, after that sort of "explanation". (...

There are already several pages on pointers in documentation (see Programmer's Guide, Community Tutorials). Fine, if they where "up to standard", which especially "Inroduction to pointers ..." is clearly not. Main issue is: the permanent reference to "reference operator *&q...

deltarho[1859] wrote:which was well off target.

You mean to say, as much as your initial off target analogy, that prompted my reply?

I've started my BSc in Computer Science, at age 40, go figure ...

I don't think deltarho[1859] was talking about actual painting I think he meant the code was more "a work of art"? Hell, I know that too. I've just wanted for once, be equally cryptic as he's usually. (Even you, as a native english speaker, needed a lot of time, to figure it out.) Why can...

Yes. From my point of view: you've no clue about spanners and probably, never had one in your hands. Why do I think so? I come from high precision mechanical engineering and am therfore, very familiar with spanners. Aka: I come from the practical side of things, while you seem to be the pure theori...

@fxm, Pointers are a pre-condition for more, than just a single part of the FB language! This definitely relates to doc. Actually meaning: your introduction part about pointers, should be made a article "in itself", because it applies to more cases, than just the "byref" stuff. (...

paul doe wrote:No. It depends on the order of the members

This is not quite true, if one knows, how to avoid padding inbetween members
(except, at the very end of a type).

Is it possible to discuss references without discussing pointers? Well, there goes another one: "Is it possible, to write about threading, without discussing pointers first?" (or at least state: you have to be confident with pointers use, to understand the following ...) There may be more...

(dodicat, no Pointers necessary, I'm afraid) If you guy's want a type, fully packed with informations ... Not yet implemented, just the structure, called Tiny_Rect (20 bytes): ' Tiny_Rect_test1.bas -- 2018-08-15, MrSwiss ' ' compile: -s console ' ' if full rectangle info in a type is required (MrSwi...