From: "Philippe Maincon" <bogus@see.below.co.za>
Path: news.mathworks.com!newsfeed-00.mathworks.com!webx
Newsgroups: comp.soft-sys.matlab
Subject: Re: Nested functions and oop
Message-ID: <ef2a03b.6@webx.raydaftYaTP>
Date: Sun, 26 Feb 2006 03:32:10 -0500
References: <ef2a03b.-1@webx.raydaftYaTP> <m3zmkg953w.fsf@coyote.llan.ll.mit.edu> <47ED96EA67AA74516EA9E9A446F55D11@in.webx.raydaftYaTP>
Lines: 27
NNTP-Posting-Host: 198.54.202.226
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Xref: news.mathworks.com comp.soft-sys.matlab:333162



Peter,

That was an interesting peep in the code, and answers more of my
inital questions about the future of oo in MATLAB. I bet this is the
syntax that was released for beta testing last year. (I was on a
dial-up line in the bush in Germany and couldn't join the feast)

Mike's call for "all methods in one file" is about to be heeded -
except for the comments that have to be in their own file (hey
MathWorks, if you start a job, do it completely! Put comments into
the main file, and reprogram "help" - OK' I'm sure you plan to do
this actually)

And there is a destructor now, of course, necessary for memmapfile to
properly close down a file access. But lack of call to destructor
does not seem to imply memory leak. You know what, I have some deep
respect those guys.

Good news of the day: this looks backward compatible with present day
syntax (well anything else would have been a serious surprise). I
don't need to send my 10.000 lines of code to the bin... Dear
MathWorks, with the next release, give us a utility that packs old
method-files into one new-syntax file, pretty please.

Cheers

Philippe