OOP is driven by the concept of classes and objects, and you cannot think that
only means buttons and fields, user interface objects only. OOP means something
quite different. Every thing you can refer to in an OOP environment MUST have a
parent class. That is what I mean by, "driven".
A
It's a scripting language. It's not the job of Livecode to do memory
management. In fact it's hardly the job of modern apps to do it. The OS manages
most of that. For us, the App is the livecode engine, and not our script.
Bob S
> On Jun 3, 2017, at 09:46 , Richmond Mathewson via
@Paul,
to defend you, it's not always so obvious to know what we can or cannot do
with regex.
@Mike
yes, Perl is great and that's certainly why I have embeded Perl in
LiveCode, Mmm, more than 10 years ago.
I've also helped some well known LiveCoders to do some complex
transformation with Perl
Thank you Thierry and everyone else.
I should have realized that I couldn't do this entirely with regex due
to the need to compare the number values. It was a long day yesterday
and my brain just wasn't in full gear.
-- Paul
On 6/5/2017 4:06 AM, Thierry Douez via use-livecode wrote:
> Hi Paul,
Wow, the perl way is pretty darn cool.
On Mon, Jun 5, 2017 at 2:06 AM, Thierry Douez via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Hi Paul,
>
>
> AFAIK you need to deal with an hybrid approach (regex + livecode)
>
> So, here is one way to do it:
>
>
>put 3 into pPage
>
>
Hi all,
Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!
Read issue #85 here: https://goo.gl/rNyg18
This is a weekly newsletter about LiveCode, focussing on what's been
going on in and around
Hi Paul,
AFAIK you need to deal with an hybrid approach (regex + livecode)
So, here is one way to do it:
put 3 into pPage
repeat for each line T in tCiCData
if matchText( T, "(?x) \t (\d+) , \d+ , (\d+) , \d+ \z", n1, n2)
then
if (n1 <= pPage) and (n2 >= pPage) then
