As you know, that's not really what I had in mind :o) but yes, that does work.


>Uh, you can do that just fine in C#:
>
>

>    public class Test
>    {
>        private object[] Args = null;
>
>        public Test(params object[] args)
>        {
>            this.Args = args;
>        }
>    }
>

>
>This allows you to pass in a variable argument list.
>
>Not sure why you'd ever want to do this rather than provide the proper type guidance which is more efficient and provides for adequate Intellisense, but there it is...
>
>+++ Rick ---
>
>>>>>>>For those VFPer sitting on the .NET fence, I just discovered this guy's blog and thought I'd share it here. I'm not trying to stir up any trouble, but, its interesting stuff and some of what he says had me laughing out loud.
>>>>>>>
>>>>>>>Check it out http://dotbloat.blogspot.com/
>>>>>>
>>>>>>Perfect thing to top a good day. For the first time for the last ten years, I took the Labor Day off - barbecue, beer etc - and this was the spiritual layered cake to make it complete.
>>>>>>
>>>>>>Even if 80% of what he says is false, the remaining 20% is enough to not touch dot net with a stool-dipped pole. Can't subclass visually? Have to write a constructor for every class? Wow.
>>>>>
>>>>>Dragan, you crack me up. I should have known you still think of May Day as a holiday. I did not know it is the Communist version of Labor Day, so thanks for that.
>>>>
>>>>Well, most of Europe, which is capitalist all over, has it as an official holiday... and it's held as a remembrance of Haymarket Massacre from which May Day was derived. And I don't mind reminding you guys every couple of years that Haymarket happened in Chicago. So most of Europe (except the Dutch, who have Queen's day the day before, and maybe a couple of others). It is, therefore, not the Communist day (though the guys were banging on it... eh, the four day weekends when 1st or 2nd would fall on a Saturday or Sunday, or even longer when not :), just your regular International Labor Day. I guess there's no international labor here, so there's only the local Labor Day. Probably when May 1st is converted from metric to imperial (the system of the Republic, eh), it falls somewhere in September ;).
>>>>
>>>>>Here's hoping all is well.
>>>>
>>>>Fine... just switched rooms with one of the daughters today. She recently became a telecommuter (reshuffling the departments in the office, so it made no more sense to keep the offices leased for the remaining four of them), and they started sending her hardware - laptop, printer and another monitor, which just couldn't fit into her room anymore.
>>>>
>>>>>PS -- You don't have to write a constructor for every class. A default constructor will be written for you if you don't want to write one yourself.
>>>>
>>>>So the code must be written... you only get some help in writing it. I'm still quite happy with three line subclassing, like
>>>>
>>>>define class myJunk as oldJunk of junk.prg
>>>>someproperty="nondefault value"
>>>>enddefine
>>>>
>>>>Laconica brevitas, eh? :)
>>>
>>>You are being stubborn. You as a developer don't have to write a constructor.
>>>
>>>But you can write as many as you like as long as the signatures are different ;-)
>>>
>>>Thank you for the edification about May Day. I still think you should write a history book.
>>
>>True, you don't have to write a constructor and writing a constructor is a small thing anyway, but having worked with VFP for so many years, it is not as flexible and you know it.
>>
>>I've gotten to where I really enjoy working in the VS2008 IDE. There are some advantages over VFP. There are two disadvantages though that are pet peeves of mine.
>>
>>1) Writing a constructor for every case of parameters that may be passed - no more multiple conditionally passed parameters in an init
>>2) Putting a breakpoint when a value changes not in a specific location