Sponsored Content
Contact Us Post Here to Contact Site Administrators and Moderators About Rules for Homework & Coursework Questions Forum Post 303029208 by RavinderSingh13 on Wednesday 23rd of January 2019 06:53:24 AM
Old 01-23-2019
Quote:
Originally Posted by Naky
Hi, in my case, I have a question for topics that are slightly dealt with in class, which I am investigating on my own but which are not directly related to the lessons.
Do I have to put the name of the school and others?
(I can't put the name of the professor because is against the school rules to share private details of person related to the school, which includes the name)
Hello Naky,

We do have strict rules and regulations for Homework questions. Where you need to provide your college/school details along with your efforts etc too. I would like to suggest you please go to forum https://www.unix.com/homework-and-coursework-questions/ once.

When you go there and then navigate to "Forum Tools --> Post a New Thread." Option. You will have to fill the complete form with all details(most importantly your efforts which you have put in order to solve your problem) and then experts will guide you on the same(please do not expect that someone will write code for you/anyone from scratch).

As I.T folks we all are welcomed here to share our problems, learning etc only main thing is NO ONE will write code for anyone from scratch, it is we will guide/or correct the code of your attempt, so it is important to mention your efforts in every post.

Please go through that forum and post sensibly. Again Welcome to this GREAT forum, where we all learn from each other.

Thanks,
R. Singh
 

6 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

suggested addition to forum rules

Possible new rule for the "forum rules" list: <UL> <LI>Include as many pertinent details as possible in your post. Useful information usually includes: Vendor and version of Unix you are using, hardware platform, kernel version (if applicable). For hardware related questions include model... (1 Reply)
Discussion started by: PxT
1 Replies

2. Post Here to Contact Site Administrators and Moderators

forum rules

i dont think this post is in the right section, but i couldnt really decide which one was appropriate, and this question seems simple enough, should normal users, ie non-moderators, tell other users if their post is in violation of the forum rules? like if a question is obviously a homework... (17 Replies)
Discussion started by: norsk hedensk
17 Replies

3. What is on Your Mind?

Forum rules

After reading the FAQ for the first time, I noticed Rule # 14 : :D:D:D Anyways, I hope to make more use of this forum in future, and also to help others. Regards Ook. :) (0 Replies)
Discussion started by: The_Librarian
0 Replies

4. Homework & Coursework Questions

Rules for Homework & Coursework Questions Forum

Homework Help: On Posting Questions: Any and all high school and undergraduate homework assignments or textbook style exercises for which you are seeking assistance are to be posted only in our Homework & Coursework Questions area--not in blogs, visitor messages, PMs, or the main technical... (0 Replies)
Discussion started by: Neo
0 Replies

5. Homework & Coursework Questions

Community Spirit and Ethos on Homework & Coursework

Helping students is in line with the "community spirit" ethos of The UNIX and Linux Forums which aims to give free help and advice in order to support the personal and professional development of others. We encourage students to think carefully about what they do, and do not, understand about... (0 Replies)
Discussion started by: Neo
0 Replies

6. Post Here to Contact Site Administrators and Moderators

2 questions about forum use

Hello 2 little questions 1) Is there a way to filter out posts so that only unanswered post appear ? 2) What is the Bits / Banking stuff for ? Thx in advance for your time & help ok i've found the answer to 1) (advanced search option) ... i have found some thread about 2) but nothing... (3 Replies)
Discussion started by: ctsgnb
3 Replies
TM::Bulk(3pm)						User Contributed Perl Documentation					     TM::Bulk(3pm)

NAME
TM::Bulk - Topic Maps, Bulk Retrieval Trait SYNOPSIS
my $tm = ..... # get a map from anywhere use TM::Bulk; use Class::Trait; Class::Trait->apply ($tm, 'TM::Bulk'); # give the map the trait # find out environment of topic my $vortex = $tm->vortex ('some-lid', { 'types' => [ 'types' ], 'instances' => [ 'instances*', 0, 20 ], 'topic' => [ 'topic' ], 'roles' => [ 'roles', 0, 10 ], 'members' => [ 'players' ], }, ); # find names of topics (optionally using a scope preference list) my $names = $tm->names ([ 'ccc', 'bbb', 'aaa' ], [ 's1', 's3', '*' ]); DESCRIPTION
Especially when you build user interfaces, you might need access to a lot of topic-related information. Instead of collecting this 'by foot' the following methods help you achieve this more effectively. names $name_hash_ref = $tm->names ($lid_list_ref, [ $scope_list_ref ] ) This method takes a list (reference) of topic ids and an optional list of scoping topic ids. For the former it will try to find the names (topic names for TMDM acolytes). If the list of scopes is empty then the preference is on the unconstrained scope. If no name for a topic is in that scope, some other will be used. If the list of scopes is non-empty, it directs to look first for a name in the first scoping topic, then second, and so on. If you want to have one name in any case, append "*" to the scoping list. If no name exist for a particular lid, then an "undef" is returned in the result hash. References to non-existing topics are ignored. The overall result is a hash (reference). The keys are of the form "topic-id @ scope-id" (without the blanks) and the name strings are the values. vortex $info = $tm->vortex (, $vortex_lid, $what_hashref, $scope_list_ref ) This method returns a lot of information about a particular toplet (vortex). The function expects the following parameters: lid: the lid of the toplet in question what: a hash reference describing the extent of the information (see below) scopes: a list (reference) to scopes (currently NOT honored) To control what exactly should be returned, the "what" hash reference can contain following components. All of them being tagged with <n,m> accept an additional pair of integer specify the range which should be returned. To ask for the first twenty, use "0,19", for the next "20,39". The order in which the identifiers is returned is undefined but stable over subsequent read-only calls. topic: fetches the toplet (which is only the subject locator, subject indicators information). names (<n,m>): fetches all names (as array reference triple [ type, scope, string value ]) occurrences (<n,m>): fetches all occurrences (as array reference triple [ type, scope, value ]) instances (<n,m>): fetches all toplets which are direct instances of the vortex (that is regarded as class here); instances* (<n,m>): same as "instances", but including all instances of subclasses of the vortex types (<n,m>): fetches all (direct) types of the vortex (that is regarded as instance here) types* (<n,m>): fetches all (direct and indirect) types of the vortex (that is regarded as instance here) subclasses (<n,m>): fetches all direct subclasses subclasses* (<n,m>): same as "subclasses", but creates reflexive, transitive closure superclasses (<n,m>): fetches all direct superclasses superclasses* (<n,m>): same as "superclasses", but creates reflexive, transitive closure roles (<n,m>): fetches all assertion ids where the vortex plays a role peers (<n,m>): fetches all topics which are also a direct instance of any of the (direct) types of this topic peers* (<n,m>): fetches all topics which are also a (direct or indirect) instances of any of the (direct) types of this topic peers** (<n,m>): fetches all topics which are also a (direct or indirect) instances of any of the (direct or indirect) types of this topic The function will determine all of the requested information and will prepare a hash reference storing each information into a hash component. Under which name this information is stored, the caller can determine with the hash above as the example shows: Example: $vortex = $tm->vortex ('some-lid', { 'types' => [ 'types' ], 'instances' => [ 'instances*', 0, 20 ], 'topic' => [ 'topic' ], 'roles' => [ 'roles', 0, 10 ], }, ); The method dies if "lid" does not identify a proper toplet. SEE ALSO
TM::Overview COPYRIGHT AND LICENSE
Copyright 200[3-57] by Robert Barta, <drrho@cpan.org> This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.10.1 2008-04-23 TM::Bulk(3pm)
All times are GMT -4. The time now is 03:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy