• Re: Why ".PS1" file extension for PS scripts?

    From Thimo Reumerman@21:1/5 to All on Mon Jan 16 07:10:37 2023
    On Saturday, February 21, 2009 at 5:37:01 PM UTC+1, RichS [MVP] wrote:
    I doubt that the 1 will be dropped anytime soon as it would be a huge breaking change
    --
    Richard Siddaway
    All scripts are supplied "as is" and with no warranty
    PowerShell MVP
    Blog: http://richardsiddaway.spaces.live.com/
    PowerShell User Group: http://www.get-psuguk.org.uk
    "Larry__Weiss" wrote:
    RichS [MVP] wrote:
    as joel said the original idea was that version would be differentiated by
    script extension. That idea has not been implemented in v2.

    #requires actually exists in v1

    To be honest it doesn't really matter how the versioning is achieved, as long as there is a way to tell PowerShell that you need v1, v2, v3 or whatever, and people remember to use it it will work

    Do you think that maybe they will drop the "1" eventually and just use ".PS" ?
    ".PS1" doesn't follow the pattern of other MS scripting language conventions.
    For example .bat .cmd .vbs
    Plus the number "1" is a particularly annoying character to use because it renders visually similar to the letter "l".

    I guess these early design decisions will haunt us forever.

    - Larry

    you were correct

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)