Have to say I agree. Had not thought of that. I was thinking more in terms of in-memory variable primitives, not in terms of containers (as C++ calls them). A list.move() function might even change the memory location of the object moved -- that might be implementation dependent.
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Saturday, July 18, 2020 5:58 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL and English was Re: Still COBOL After All These Years? > What exactly would "move" mean in a computer memory context? Moving an element from one list to another comes to mind. That doesn't change the physical location of the data, but it does change their logical location. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
