Date: Mon, 9 Jun 2025 13:55:32 -0500
On Mon, Jun 9, 2025 at 12:13 PM Jason McKesson via Std-Proposals <
std-proposals_at_[hidden]> wrote:
> On Mon, Jun 9, 2025 at 9:25 AM Frederick Virchanza Gotham via
> Std-Proposals <std-proposals_at_[hidden]> wrote:
> >
> > Paper attached to this email in HTML format. Hasn't been published yet.
> >
> > Link to this version:
> > http://virjacode.com/papers/polyhandle_unpublished000.htm
> >
> > Link to the latest version:
> > http://virjacode.com/papers/polyhandle.htm
>
> I find it interesting that this "proposal" spends over a dozen
> paragraphs on the minor question of "how would this be implemented",
> while the most important question of "is this actually useful" is hand
> waved away with "There are many situations where it is useful". Like,
> why would a reflection system care if a type-erased object is
> polymorphic? Come to think of it, why would something using reflection
> use a *type-erased pointer* at all?
>
[...]
> I find this interesting... but not surprising.
>
It would be more useful to provide the feedback with less sarcasm and
abrasion. Just say what the paper is missing, why it's badly structured,
and if you feel like it and provide pointers and direction as to getting
help improving it. We've been new at writing papers at some point.
PS. Yes, I'm aware of that other thread regarding this paper. And that
context still doesn't justify the insuations here.
std-proposals_at_[hidden]> wrote:
> On Mon, Jun 9, 2025 at 9:25 AM Frederick Virchanza Gotham via
> Std-Proposals <std-proposals_at_[hidden]> wrote:
> >
> > Paper attached to this email in HTML format. Hasn't been published yet.
> >
> > Link to this version:
> > http://virjacode.com/papers/polyhandle_unpublished000.htm
> >
> > Link to the latest version:
> > http://virjacode.com/papers/polyhandle.htm
>
> I find it interesting that this "proposal" spends over a dozen
> paragraphs on the minor question of "how would this be implemented",
> while the most important question of "is this actually useful" is hand
> waved away with "There are many situations where it is useful". Like,
> why would a reflection system care if a type-erased object is
> polymorphic? Come to think of it, why would something using reflection
> use a *type-erased pointer* at all?
>
[...]
> I find this interesting... but not surprising.
>
It would be more useful to provide the feedback with less sarcasm and
abrasion. Just say what the paper is missing, why it's badly structured,
and if you feel like it and provide pointers and direction as to getting
help improving it. We've been new at writing papers at some point.
PS. Yes, I'm aware of that other thread regarding this paper. And that
context still doesn't justify the insuations here.
-- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supongas Nada -- Robot Dreams - http://robot-dreams.net
Received on 2025-06-09 18:55:50