home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!nntp-server.caltech.edu!peri
- From: peri@cco.caltech.edu (Michal Leah Peri)
- Newsgroups: soc.couples
- Subject: Re: A Question...
- Date: 24 Jan 1993 06:26:26 GMT
- Organization: California Institute of Technology, Pasadena
- Lines: 36
- Message-ID: <1jtcqiINNqjn@gap.caltech.edu>
- References: <106120@netnews.upenn.edu> <thurlow.727855086@convex.convex.com>
- NNTP-Posting-Host: sandman.caltech.edu
- Keywords: last names
-
- thurlow@convex.com (Robert Thurlow) writes:
-
- >In <106120@netnews.upenn.edu> pezzillo@eniac.seas.upenn.edu (Amy J. Pezzillo) writes:
-
- >>Here's a question that I'd like people's opinions on: What do you
- >>think about the practice of a woman taking the man's last name when
- >>they get married?
-
- The same as I think of a man taking his wife's name:
-
- It's a legal hassle. (All those forms!)
-
- It provides an opportunity for unscrupulous parties to take advantage
- of you. (eg, those companies that solicit business by offering to fill
- out your forms and pay your $50 fee for changing your name -- when there
- is no $50 fee!)
-
- It can mess up your credit history.
-
- It confuses your employer and your co-workers.
-
- It can wreck havoc with your health insurance and life insurance.
-
- You can lose your employment history. (If you've established a name
- name for yourself and a good reputation you're liable to lose.)
-
- It makes it much harder (or impossible) for old friends to look you
- up. ("She got married and I don't know what her name is now!")
-
-
-
- --
-
- -- Michal
- ----------------------------------------------------------------------
- Impressive amounts of material can be accreted in this manner.
-