git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Vajna <vmiklos@frugalware.org>
To: Olivier Marin <dkr+ml.git@free.fr>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Junio C Hamano <gitster@pobox.com>,
	Don Zickus <dzickus@redhat.com>,
	git@vger.kernel.org
Subject: [PATCH] path-list documentation: document all functions and data structures
Date: Sat, 14 Jun 2008 02:56:04 +0200	[thread overview]
Message-ID: <1213404964-25161-1-git-send-email-vmiklos@frugalware.org> (raw)
In-Reply-To: <48530331.70807@free.fr>

Signed-off-by: Miklos Vajna <vmiklos@frugalware.org>
---

Updated patch, obviously we want to init the struct with '\0', not '0'.

 Documentation/technical/api-path-list.txt |   92 +++++++++++++++++++++++++++-
 1 files changed, 88 insertions(+), 4 deletions(-)

diff --git a/Documentation/technical/api-path-list.txt b/Documentation/technical/api-path-list.txt
index d077683..313d088 100644
--- a/Documentation/technical/api-path-list.txt
+++ b/Documentation/technical/api-path-list.txt
@@ -1,9 +1,93 @@
 path-list API
 =============
 
-Talk about <path-list.h>, things like
+The path_list API offers a data structure and functions to handle sorted
+and unsorted string lists.
 
-* it is not just paths but strings in general;
-* the calling sequence.
+The name is a bit misleading, a path_list may store not only paths but
+strings in general.
 
-(Dscho)
+The caller:
+
+. Allocates and clears (`memset(&list, \'\0', sizeof(list));`) a
+  `struct path_list` variable.
+
+. Initializes the members. You can manually set the `items` member, but
+  then you have to set `nr`, accordingly. Also don't forget to set
+  `strdup_paths` if you need it.
+
+. Adds new items to the list, using `path_list_append` or `path_list_insert`.
+
+. Can check if a string is in the list using `path_list_has_path` or
+  `unsorted_path_list_has_path` and get it from the list using
+  `path_list_lookup` for sorted lists.
+
+. Can sort an unsorted list using `sort_path_list`.
+
+. Finally it should free the list using `path_list_clear`.
+
+Functions
+---------
+
+* General ones (works with sorted and unsorted lists as well)
+
+`print_path_list`::
+
+	Dump a path_list to stdout, useful mainly for debugging purposes. It
+	can take an optional header argument and it writes out the
+	string-pointer pairs of the path_list, each one in its own line.
+
+`path_list_clear`::
+
+	Free a path_list. The `path` pointer of the items will be freed in case
+	the `strdup_paths` member of the path_list is set. The second parameter
+	controls if the `util` pointer of the items should be freed or not.
+
+* Functions for sorted lists only
+
+`path_list_has_path`::
+
+	Determine if the path_list has a given string or not.
+
+`path_list_insert`::
+
+	Insert a new element to the path_list. The returned pointer can be handy
+	if you want to write something to the `util` pointer of the
+	path_list_item containing the just added string.
+
+`path_list_lookup`::
+
+	Look up a given string in the path_list, returning the containing
+	path_list_item. If the string is not found, NULL is returned.
+
+* Functions for unsorted lists only
+
+`path_list_append`::
+
+	Append a new string to the end of the path_list.
+
+`sort_path_list`::
+
+	Make an unsorted list sorted.
+
+`unsorted_path_list_has_path`::
+
+	It's like `path_list_has_path()` but for unsorted lists.
+
+Data structures
+---------------
+
+* `struct path_list_item`
+
+Represent an item of the list. The `path` member is a pointer to the
+string, and you may use the `util` member for any purpose, if you want.
+
+* `struct path_list`
+
+Represents the list itself.
+
+. The array of items are available via the `items` member.
+. The `nr` member contains the number of items stored in the list.
+. The `alloc` member is used for `ALLOC_GROW()`.
+. Setting the `strdup_paths` member to 1 means that the added paths are
+  copied to the path list and not just a pointer to them is stored.
-- 
1.5.6.rc2.dirty

  parent reply	other threads:[~2008-06-14  0:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13 16:55 [PATCH] git-apply doesn't handle same name patches well Don Zickus
2008-06-13 20:32 ` Johannes Schindelin
2008-06-13 20:42   ` Don Zickus
2008-06-13 22:48   ` [PATCH] path-list documentation: document all functions and data structures Miklos Vajna
2008-06-13 23:30     ` Olivier Marin
2008-06-14  0:13       ` Miklos Vajna
2008-06-14  0:56       ` Miklos Vajna [this message]
2008-06-14 12:50         ` Olivier Marin
2008-06-14 22:50           ` Miklos Vajna
2008-06-14 18:08         ` Johannes Schindelin
2008-06-14 23:22           ` Miklos Vajna
2008-06-15  9:01             ` Jakub Narebski
2008-06-15 12:06               ` Miklos Vajna
2008-06-15  5:04           ` Junio C Hamano
2008-06-16  9:01 ` [PATCH] git-apply doesn't handle same name patches well Mike Ralphson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1213404964-25161-1-git-send-email-vmiklos@frugalware.org \
    --to=vmiklos@frugalware.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dkr+ml.git@free.fr \
    --cc=dzickus@redhat.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).