From: Matthieu Dubuget <matthieu.dubuget@gmail.com>
To: florent.ouchet@imag.fr
Cc: Caml Mailing List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Java JVM is becoming more strict
Date: Fri, 25 Mar 2011 11:20:13 +0100 [thread overview]
Message-ID: <4D8C6C5D.8000502@gmail.com> (raw)
In-Reply-To: <4D8C684D.3040702@imag.fr>
-------- Original Message --------
Subject: Re: [Caml-list] Java JVM is becoming more strict
From: Florent Ouchet <florent.ouchet@imag.fr>
To: matthieu.dubuget@gmail.com
Date: 25/03/2011 11:02
> Hello Matthieu,
>
> Is your application a console application or a GUI application? In the
> second case, I've already seen cases where STDIN/STDOUT/STDERR pipes
> are completly invalid while it does work in other cases.
That's it. This is a GUI ultrasonic data acquisition system. The DLL is
used to process som datas.
next prev parent reply other threads:[~2011-03-25 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 8:21 Matthieu Dubuget
2011-03-25 10:02 ` Florent Ouchet
2011-03-25 10:20 ` Matthieu Dubuget [this message]
2011-03-25 12:57 ` Florent Ouchet
2011-03-25 16:14 ` Matthieu Dubuget
2011-03-26 13:13 ` Dmitry Bely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D8C6C5D.8000502@gmail.com \
--to=matthieu.dubuget@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=florent.ouchet@imag.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).