Title: util
Evrika Group - cursuri de perfectionare :
- contabilitate costul cursului este de 300 ron cu incepere din 25 ianuarie 2009 .
- expert fiscal costul cursului este de 1000 ron cu incepere in 21 ianuarie 2009.
- inspector protectia munc
On Sat, Dec 13, 2008 at 1:24 PM, Rick McGuire wrote:
> There's only one init method, which is normally called by the new
> method of the class object. The normal pattern if you wish to have
> multiple versions of "new" is to have the additional class methods
> call new, then perform any addition
There's only one init method, which is normally called by the new
method of the class object. The normal pattern if you wish to have
multiple versions of "new" is to have the additional class methods
call new, then perform any additional initialization after new
completes. For example, .array~of
What would be the proper way to implement something like:
a = .array~new
b = .array~of(1, 2, 3,)
using the native API for a new class?
In other words, I want to define a new class where there are several
different *sets* of initialization options that can be used to create
the new object. R
Hi Mark,
well I was in the middle of composing that tracker item when I found
that I didn't know what I was talking about. I shall now go ahead and
recompose and submit it.
thanks for this and all your work on ooDialog. It is very impressive!
Jon
2008/12/13 Mark Miesfeld :
> On Sat, Dec 13, 2
On Sat, Dec 13, 2008 at 1:37 AM, Sahananda (Jon) Wolfers
wrote:
> This is what I think is the case:
> 1) what used to be described as ooDialog external functions still
> exist and are callable in 4.0.0 with the exception of instMMfuncs
Everything that was documented in 3.2.0, should work in 4.0.
OK,
my last reply has demonstrated that I don't understand what is going on here.
This is what I think is the case:
1) what used to be described as ooDialog external functions still
exist and are callable in 4.0.0 with the exception of instMMfuncs
2) You no longer need to load them - you can just
