Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create a new page with info about OS portability #670

Open
AlexDaniel opened this issue Jul 5, 2016 · 4 comments
Open

Create a new page with info about OS portability #670

AlexDaniel opened this issue Jul 5, 2016 · 4 comments
Labels
docs Documentation issue (primary issue type)
Milestone
2023-Quarter 4

Comments

@AlexDaniel
Copy link
Member

Part of #657:

Tutorials:
    * OS portability details

But what kind of details?
@AlexDaniel AlexDaniel added the docs Documentation issue (primary issue type) label Jul 5, 2016
AlexDaniel added a commit that referenced this issue Jul 5, 2016
@AlexDaniel
WANTED file is not needed anymore (#657)
30f81a5 
Here is the summary of all items in WANTED list (and reasons why we do not
need to list them anymore):

Tutorials:
    * general Perl 6 intro 〈listed in #114〉
    * multis / multi dispatch, how to use them practically 〈/language/functions#Multi-dispatch as well as /type/Signature#Type_Constraints〉
    * lazy lists and generators 〈issue #667〉
    * concurrency 〈/language/concurrency〉
    * IO 〈/language/io〉
    * network programming (e.g., examples for IO::Socket::INET) 〈#114 lists “FAQ: Web & Networking: Dealing with the Web, Email & networks”, that's probably enough〉
    * MOP 〈/language/mop〉
    * When to use which Set/Bag/*Hash type 〈#668〉
    * Regexes and grammars (can be partially stolen from perl6/book) 〈language/regexes and language/grammars〉
    * Pod6 〈#669
    * Exceptions 〈/language/exceptions〉
    * Updated version of http://perl6advent.wordpress.com/2010/12/22/day-22-the-meta-object-protocol/ (RT #121967) 〈not relevant anymore? no such example in the docs〉
    * OS portability details 〈#670

Syntax features:
    * Hyper Operators (prefix, infix, postfix and method call) 〈language/operators#Hyper_Operators〉
    * $*ARGFILES, lines()   (Issue #96) 〈issue #96 is closed〉
    * dispatch related declarators:  multi, only, proto, method, etc... 〈#634 #671〉
    * Smartmatching: ~~, allowed RHS values, backlinks from related docs (grep) 〈#672〉

API docs:
    * KeyReducer 〈#673〉
    * Uni 〈/type/Uni ?〉

Functions:
    * srand() 〈#674〉
    * use [probably really important...] 〈what?〉
    * on (S17) 〈we have /language/concurrency, it is probably good enough〉
    * duckmap() and deepmap() 〈#675 #676〉

Miscellaneous:
    * Add TODO comments to undocumented items ("=comment TODO") (Have started - dha) 〈we now use github issues instead〉
@AlexDaniel
Copy link
Member Author

For example, details on how \r\n and \n are handled.

@JJ JJ added the wishlist "nice to have" issues; might require a lot of work or a big change or be low priority label Feb 10, 2018
@JJ
Copy link
Contributor

JJ commented Mar 13, 2018

In a new page?

@AlexDaniel
Copy link
Member Author

Preferably, yes. I think it would be better to have all OS-related info on one page.

@JJ JJ changed the title Add info about OS portability Create a new page with info about OS portability Mar 13, 2018
@JJ JJ self-assigned this Apr 17, 2018
@JJ JJ removed the JJ TPF Grant label May 14, 2018
@coke coke unassigned JJ Feb 4, 2023
@raiph
Copy link
Contributor

raiph commented Oct 27, 2023

"It may also be worth mentioning in some Raku document somewhere that distributions should not contain symlinks if they are expected to be platform agnostic.".

Note that this was prompted by an installation issue that arose for a Raku distribution that was shared, not an issue with running Rakudo or a Raku program once a package had been installed, but I agree with @AlexDaniel that it would be better to have all OS portability info on a single page, at least until it's huge. (And given that it's remained non-existent for 7 years, I'm thinking we don't need to worry about that for now!)

@coke coke removed the wishlist "nice to have" issues; might require a lot of work or a big change or be low priority label Oct 27, 2023
@coke coke added this to the 2023-Quarter 4 milestone Oct 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
docs Documentation issue (primary issue type)
Projects
None yet
Milestone
2023-Quarter 4
Development

No branches or pull requests
4 participants
@JJ @coke @raiph @AlexDaniel