Heads up, don't use "secure" as a handler name
janschenkel at yahoo.com
Mon Sep 12 10:16:39 EDT 2011
Hi Jacque et al,
While it doesn't appear in the dictionary as a separate keyword, 'secure' was introduced into the language in version 2.5, as part of the SSL support for 'open socket' - see: <http://docs.runrev.com/Command/open-socket>
Perhaps the current version of the compiler is a little more picky than previous iterations. At any rate, it might be good to file a documentation bug, and suggest that 'secure' gets a separate entry, a bit like the 'effective' keyword.
Quartam Reports & PDF Library for LiveCode
"As we grow older, we grow both wiser and more foolish at the same time." (La Rochefoucauld)
----- Original Message -----
From: J. Landman Gay <jacque at hyperactivesw.com>
To: How to use LiveCode <use-livecode at lists.runrev.com>
Sent: Sunday, September 11, 2011 1:30 AM
Subject: Re: Heads up, don't use "secure" as a handler name
On 9/10/11 5:25 PM, Mark Wieder wrote:
> I can get secure() and it shows the answer dialog and returns my
> value, but I can't compile "put secure()". I don't think I've ever
> seen a function that I could get but not put.
I think there's a little "oops" in the engine. I can't decide whether to report it or leave it as a surprise. I mean, how many people write functions named "secure"?
-- Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode