caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] STOP (was: Search for the smallest possible possible	Ocaml segfault)
Date: Thu,  8 Nov 2007 20:06:43 +0100	[thread overview]
Message-ID: <1194548803.47335e4348ebb@webmail.in-berlin.de> (raw)
In-Reply-To: <47334DAA.80407@inria.fr>

Hello Xavier,


Zitat von Xavier Leroy <Xavier.Leroy@inria.fr>:

> Guys,
>
> Before posting this kind of messages, I'd like you to stop for a
> second and think about what you're doing.  The answer is: a disservice
> to the Caml community.
[...]

I hope that nobody has intended this.
And I doubt that people wanted to disservice the OCaml-community.

For me OCaml is the best language I've used.
I think, most people here will agree.

Segfaults in OCaml are seldom, but nevertheless
those seldom seen segfaults should be fixed.

The original poster stated out that the bug he
posted was four months on status "new".

This was a littlebid astonishing, and possibly
the reason why this thread was started.


[...]
> Yes, OCaml has bugs, like all software of this complexity -- and
> probably a lot less than your own software.  Be supportive and
> cooperative: post bug reports with repro cases where they belong, on
> the bug tracking system, and let us developers handle them the way we
> see fit.
[...]

Yes, I agree here.

But it's not so easy to find a real bug in Ocaml,
so people might not be motivated to make a login-account
on the bugtracker and remember another password for
something that seldom is in use. ;-)


>
> That kind of snickering posts is neither helpful nor supportive.

I hope theese bugs will be all reported.
And also I hope, they will be fixed then.

I hope that you don't get any trouble from theese posts.


I for myself have only stated that I hope the bugs will be fixed.

The thing that I laughed about, really was a joke,
because sending SIGSEGV to PID = 0 means that the program
has to abort with a SIGSEGV, because it sends that signal to itself.

So, this was NOT a Ocaml-bug, and it was NOT a bug at all.
So, I think laughing about that is NOT laughing about OCaml.


I hope you can see this thread with humor, if not today,
maybe later.


There is no reason for you to be bothered here.
Your work is undisputed.


Best Regards,
     Oliver Bandel


  parent reply	other threads:[~2007-11-08 19:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 14:17 Search for the smallest possible possible Ocaml segfault Till Varoquaux
2007-11-08 15:00 ` [Caml-list] " Jean-Christophe Filliâtre
2007-11-08 15:17   ` Till Varoquaux
2007-11-08 15:55     ` Adrien
2007-11-08 16:05 ` Alain Frisch
2007-11-08 16:30   ` Feature request (was Re: [Caml-list] Search for the smallest possible possible Ocaml segfault....) Martin Jambon
2007-11-08 18:23     ` Martin Jambon
2007-11-08 16:07 ` [Caml-list] Search for the smallest possible possible Ocaml segfault Jeremy Yallop
2007-11-08 16:11   ` Jeremy Yallop
2007-11-08 16:17     ` Till Varoquaux
2007-11-08 17:02       ` Stefano Zacchiroli
2007-11-08 17:10         ` Till Varoquaux
2007-11-08 17:02       ` Pascal Zimmer
2007-11-08 17:12         ` Oliver Bandel
2007-11-08 17:11 ` Oliver Bandel
2007-11-08 17:13 ` Zheng Li
2007-11-08 17:55 ` [Caml-list] STOP (was: Search for the smallest possible possible Ocaml segfault) Xavier Leroy
2007-11-08 18:11   ` Tom Primožič
2007-11-08 18:23     ` [Caml-list] STOP Robert Fischer
2007-11-08 19:01       ` Basile STARYNKEVITCH
2007-11-08 18:31   ` [Caml-list] STOP (was: Search for the smallest possible possible Ocaml segfault) Till Varoquaux
2007-11-08 19:06   ` Oliver Bandel [this message]
2007-11-09 18:09     ` Pierre Weis
2007-11-10 14:32       ` OCaml's formatting libraries Bünzli Daniel
2007-11-10 14:58         ` [Caml-list] " Jon Harrop
2007-11-10 15:43           ` Bünzli Daniel
2007-11-10 19:13             ` Jon Harrop
2007-11-13  9:22               ` Pierre Weis
2007-11-13  9:13             ` Pierre Weis
2007-11-13  8:53         ` Pierre Weis

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=1194548803.47335e4348ebb@webmail.in-berlin.de \
    --to=oliver@first.in-berlin.de \
    --cc=caml-list@inria.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).