Re: constructors

From: David White (no_at_email.provided)
Date: 09/01/04 

Date: Wed, 1 Sep 2004 12:17:19 +1000

"Mike Wahler" <mkwahler@mkwahler.net> wrote in message
news:rC6Zc.4019$8d1.1427@newsread2.news.pas.earthlink.net...
> Employee emp(1,
> "12 Madison Ave",
> "123-4567",
> 100,
> "I. M. Great",
> 1000,
> 0.4);

This might not comply with the requirement to create the object
"dynamically", depending on exactly what that was supposed to mean in this
case. If not, then the OP should stick with his/her original code for this
part.

DW

Relevant Pages

  • Re: Relational-to-OOP Tax
    ... depending on the size of the SQL statements ... cleaner or more well-factored code. ... insert into employee values ...
    (comp.object)
  • Re: block remote desktop
    ... depending on their importance to the company. ... they have no regard for company policy. ... He is just like any employee who takes offense to ...
    (microsoft.public.windowsxp.general)
  • Time tracking problem
    ... I am developing an employee log-in database. ... their id and pw and they are logged in or out depending on previous status. ... Now the client would like a form where they can check/approve/manipulate the ...
    (microsoft.public.access.forms)
  • Re: Hourly rate changes in payroll system
    ... Another field that is often affected by this type or change is Employee ... Depending on how long you keep records of non-current employees, ... original report and payroll check or do you want it to show the current ... to use the history report. ...
    (microsoft.public.access.forms)
  • Re: Is this the correct form of a copy constructor?
    ... Mike Wahler wrote in message ... > as const. ... Depending on what exactly you mean by "does not modify the object". ...
    (comp.lang.cpp)