in reply to Let shortcut types have useful behavior in the parameterless case

apc:// has had a no-target default since it was created.

And I agree with tye that any handler that doesnt have a sane no-target possibility should foward to the appropriate documentation page.

---
$world=~s/war/peace/g

  • Comment on Re: Let shortcut types have useful behavior in the parameterless case

Replies are listed 'Best First'.
Re^2: Let shortcut types have useful behavior in the parameterless case
by jdporter (Paladin) on Aug 15, 2006 at 17:24 UTC
    any handler that doesnt have a sane no-target possibility should foward to the appropriate documentation page

    That's a reasonable thing to do, but to my mind a better approach would be to let [foo://] DWIM from the writer's POV. IOW, if I want to link to the Perl Changes Browser, I write [apc://] If I want to link to the Wiki Wiki Web, I write [c2://]. If I want to link to the Perl docs, I write [doc://]. If I want to link to Wikipedia, I write [wp://]. And so on. Rather than assuming the author made an error.

    There's precedent for both approaches ([id://] vs. [apc://]). However, given that [id://] doesn't have any other useful default semantics, I'm not convinced that this is the precedent to follow. I'd rather follow the [apc://] precedent.

    We're building the house of the future together.
[reply]
[d/l]
[select]
      I think you misread. demerphq specified the handlers without "a sane no-target possibility" (e.g. the handlers for "http", "id" and similar) should link to docs on how to use them, not all of handlers.
[reply]

        You're right - I did misread.

[reply]

In Section Inner Scriptorium