caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jeff Schultz <jws@csse.unimelb.edu.au>
To: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] [community poll for PR#5312] Do some OCaml Windows users still use the @responsefile feature?
Date: Tue, 6 Mar 2012 00:46:24 +1100	[thread overview]
Message-ID: <20120305134624.GA5718@mulga.csse.unimelb.edu.au> (raw)
In-Reply-To: <CAPFanBEgqetA==x4z18ochvtBzd1gAy8wiK4sGboDpfD8D5egQ@mail.gmail.com>

On Mon, Mar 05, 2012 at 11:46:08AM +0100, Gabriel Scherer wrote:
> According to our Windows spies, the command-line restrictions are
> nowadays very reasonable: 8K for cmd.com, and 32K internally. Maybe
> the @responsefile feature has outlived its use, and this bug could be
> fixed by simply removing the @-files expansion phase of the runtime.

8K is not much.

> This change would however affect all user programs, so it should not
> be taken lightly; it could break your programs.

> What do OCaml Windows user think? Do you still rely on @reponsefile?
> Please complain if you do -- or your users do -- and don't hesitate to
> pass the question to off-list OCaml Windows users.

I stopped using OCaml for new development *because* of the pain it
caused on MSWIN, so my opinion is probably not very valuable.

It looks to me like you could simply disable the feature for arguments
following -w.  However, if you want to remove the feature, I suggest
that you do so in three stages:

    1.  Disable the @responsefile feature and provide a command line
	flag to reenable it.  Warn if this conflicts with the -w @a
	style of options.
    2.  In a later release, remove the code, but make the flag print
	an appropriate diagnostic.
    3.  In an even later release, remove the flag completely.

The time between the first two steps should be determined by the
response to the first step.

This is the standard evolution: make people notice that you are taking
a feature away, but let them keep using it, followed by taking it
away, but telling them it's gone, followed by pretending it never
existed.

It's good that you're adding the desirable preliminary of asking
first.


    Jeff Schultz

  parent reply	other threads:[~2012-03-05 13:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05 10:46 Gabriel Scherer
2012-03-05 11:02 ` David Allsopp
2012-03-05 12:02   ` Romain Bardou
2012-03-05 13:06 ` Adrien
2012-03-05 13:46 ` Jeff Schultz [this message]
2012-03-05 13:55   ` Dmitry Grebeniuk
2012-03-05 14:31   ` Gabriel Scherer
     [not found]     ` <20120305151021.GA26422@mulga.csse.unimelb.edu.au>
2012-03-05 15:51       ` Gabriel Scherer
2012-03-05 18:37   ` Gerd Stolpmann
2012-03-05 12:46 Damien Guichard

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=20120305134624.GA5718@mulga.csse.unimelb.edu.au \
    --to=jws@csse.unimelb.edu.au \
    --cc=caml-list@yquem.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).