| To: | REALbasic Betas <realbasic-betas at lists dot realsoftware dot com> |
|---|---|
| Subject: | Re: Ability to have more then one Return Value |
| From: | Theodore H. Smith <delete at softhome dot net> |
| Date: | Sun, 28 Jul 2002 15:11:48 +0200 |
Besides, in response to a previous message, ByRef is not a kludge. If you understand what it's actually doing, you'll see it's perfectly fine. And it also has other uses, namely if you have a 2MB string you don't want to copyit, so you pass it around ByRef. This is RS's fault that you think that. They should have documented the string behaviour. I documented it on my website though. But basically, strings are a bit like objects. They are references to the actual data. So
s2 = s1
does NOT copy the data, but copies a reference.
--
Theodore H. Smith - Macintosh Consultant / Contractor.
My website: <www.elfdata.com/>
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Vector3D ops on nil objects, Nick Dabner |
|---|---|
| Next by Date: | Re: Ability to have more then one Return Value, Geoff Canyon |
| Previous by Thread: | Re: Ability to have more then one Return Value, Stéphane Pinel |
| Next by Thread: | Re: Ability to have more then one Return Value, Emile Schwarz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |