Perhaps program yourself a simulated girl.
It won't get you anywhere near real women, ..but
you may have to settle for a simulation.

Noobie Java questions should be addressed to comp.lang.java.help.

.ed

--
www.EdmundKirwan.com - Home of The Fractal Class Composition.

Try using 'long'.

/JN

I would look at working on my communications skills.

Try java.net.Socket.

Just be glad you are not a C programmer, then you would definatly need
some pointers.

how about applying reflection mechanism on girl !!

Eliot Coweye said something like:

Read these two quick posts of mine, from the same thread.  You may learn
something critical that will save you with girls.

http://groups.google.com/group/alt.sys.pc-clone.dell/msg/85564143d0f3fbb8

http://groups.google.com/group/alt.sys.pc-clone.dell/msg/9bf00ee662c894fb

...[rip]...

Maybe the problem is that you are trying to solve a hardware problem with
software?

Here is a possible hardware solution: http://www.fu-fme.com/

Rhino

So you'd like to evade a void? No problem. Listen up...

First things first: get in super.Shape. Next: all your URLs should be created
with protocol "female", same with URI schemes. As a consequence, you'll notice
that your GeneralPath will lead you into Area(s) populated heavily with public
class Women.

Secondly, as the Window of opportunity tends to be very narrow, don't lose
Focus! Make sure that a lot of instances of public class Woman have
FocusTraversalPolicy set on you.

Thirdly, implement as much Listeners as possible (public class Women like being
listened to). Then you have to establish a Connection (some PreparedStatement
might come in handy), followed by Identity. Remember that Naming.lookup() is a
great ice breaker.

After a while, you have to broaden the IdentityScope. Visit some KeyFactory and
then exchange your public Keys. Don't think you're home free, though. GC also
comes with the package. You'll also have to learn to be a good Observer. Your
Observable will like that very much.

Further more, the trick is to use a long, Long or Big* member (field). Put it to
work in an inner Socket, preferably doing it safely (SSLSocket). Catch all the
Exceptions in all the OutputStream(s) unless you explicitly want child
Processes. Moreover, don't rely on your average BasicStroke, you have to come up
with some versatile method(s). Extending the built-in Socket(s) with something
like Suckit(s) might also impress some public class Woman, but some don't like
using MulticastSocket(s). Speaking of which, allways check the .getPreferred*()
beforehand. Otherwise you might have to deal with nasty Throwables, like
IllegalAccessError. Also take into account that NoSuchMethodError means
NoSuchMethodError (same for NoSuchFieldError and the analogous Exceptions).
Having dealt with all that, make sure that you close all the necessary ports on
your firewall, because InterruptedExceptions tend to be very destructive (plus
your Reference will become a SoftReference (i.e. your RoundingMode will switch
from UP to DOWN) for an indefinite period of time).

Sooner or later you'll have to realize that the best you can do is to make your
instance of public class Woman final and static. It's not unusual that in the
process you also make it private, though protected might also work in some
cases. Of course, you'd have to say goodbye to Swing for as long as you both
shall live.

Grooming usually is helpful.

Good Java progammers make good money,
and good money attracts girls.

   Lookup genetic programming.

http://en.wikipedia.org/wiki/Genetic_programming
http://www.cs.ucl.ac.uk/research/genprog/gp2faq/gp2faq.html

   What you'll want to do is to programmatically enter in every strategy
you've tried at hooking up with a girl. You'll need to have some metric for
measuring success, and enter those in for each strategy as well. Then run
one step of simulation (i.e. one generation) so that the strategies will
have mutated slightly, with the strategies that have performed the best
mutating the least (thus, on average, your strategies have become "better").

   Examine what strategies were produced, and go out and try them. Measure
their success, come back and enter in their scores, and progress another
generation. Repeat until you are satisfied with the level of success you are
receiving.

   The advantages of genetic programming are that it's a viable tool for
when you have no idea where to start looking for a good strategy.

   The disadvantages are that typically it takes a very long before the
best strategy "evolves" from your initial pool of random strategies.

   - Oliver