unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: A via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha@sourceware.org
Subject: More string functions.
Date: Mon, 14 Nov 2022 14:21:17 +0530	[thread overview]
Message-ID: <CAOM0=dbhfyeyL-exFZ44XeYeEy9E=GUHwkM-E7yj5ak_PB5Zfw@mail.gmail.com> (raw)

Hi,

I am implementing the following string functions in C. Some of them I
have already implemented. They can be found
here:https://marc.info/?l=linux-kernel&m=166745670428635&w=2

I just wanted to know whether glibc would be interested in these
functions. Obviously, if glibc is interested then I may have to change
my code and may be coding style too.

I am not expecting any negative comments about this request and about my code.

If glibc is not interested, then please silently ignore this mail.

The functions are:

Functions implemented are:
-------------------------------------

str_split()
str_join()
substr()
get_input_from_stdin_and_discard_extra_characters()
str_is_null_or_empty()
str_is_whitespaces()
str_is_null_or_empty_or_whitespaces()
str_is_integer()
str_starts_with()
str_ends_with()
str_join()
substr()
str_split()
get_number_of_strings_in_strings_array()
print_strings_array()
free_strings_array()

Functions to implement are:
-------------------------------------

str_is_float()
str_is_ascii()
str_strip()
str_strip_leading()
str_strip_trailing()
str_trim()
str_trim_leading()
str_trim_trailing()
str_compare_range()
str_hash_code()
str_remove_leading_characters()
str_remove trailing_characters()
str_r_str()
str_to_lower_case()
str_to_upper_case()
strtok_new()
str_left_pad(char, count)
str_right_pad(char, count)
str_replace_str()
str_replace_chr()
str_insert_str()
str_insert_chr()
str_remove_str()
str_remove_chr()
str_repeat(int count)
str_shuffle()
str_format_in_usa_currency()
get_file_name_from_path()
get_parent_directory_of()

// regex functions
str_match_regex()
str_starts_with_regex()
str_ends_with_regex()
str_replace_regex()
str_remove_regex()
str_split_on_regex_delim()

Amit

                 reply	other threads:[~2022-11-14  8:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

  List information: https://www.gnu.org/software/libc/involved.html

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

  git send-email \
    --in-reply-to='CAOM0=dbhfyeyL-exFZ44XeYeEy9E=GUHwkM-E7yj5ak_PB5Zfw@mail.gmail.com' \
    --to=libc-alpha@sourceware.org \
    --cc=amit234234234234@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).