Re: [MacPerl] Perl app framework (Using ' instead of :: ...)

[Chris Nandor <pudge@pobox.com>]

At 15.32 -0500 2000.03.10, David Ackerman wrote:
>On Fri, 10 Mar 2000, Chris Nandor wrote:
>
>> At 1.55 -0500 2000.03.10, Joshua Juran wrote:
>> >Right.  But to be pedantic, it's not the access to powerful functions /per
>> >se/ that's dangerous, but the unfiltered interface to them.
>>
>> I somewhat disagree.  First, MacPerl's toolbox modules are not entirely
>> stable.  There are bugs.  So this is the first problem.  Second, even a
>> filtered interface, without background inteligence, can be dangerous.  If I
>> call MacWindow->new, I can still pass it bad arguments.  The danger is
>> reduced, but not eliminated.
>
>Is there a place where these bugs are documented?

I dunno.


>Also, I'm wondering if the object interfaces present in the toolbox
>modules take care of all memory management for us?  For example, if I call
>new MacColorWindow (5000);
>
>is the resource made non-purgable by MacColorWindow?  Does it move the
>handle to the window hi in memory and lock it?  Or do we still need to
>handle those details when using the object interface?
>
>Sorry if this is a stupid question.  I'm working on a script which will
>rely heavily on the toolbox for certain interface elements, and I want to
>make it as stable as possible.

I don't use it enough to give you definite good answers.  Maybe Kevin Reid
or Matthias is listening.

-- 
Chris Nandor          mailto:pudge@pobox.com         http://pudge.net/
%PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10  1FF77F13 8180B6B6'])

# ===== Want to unsubscribe from this list?
# ===== Send mail with body "unsubscribe" to macperl-request@macperl.org