Issue 128 in toped: string routines

[to...@googlecode.com]

Status: New
Owner: analogc...@gmx.net
Labels: Type-Enhancement Priority-Medium OpSys-All Usability

New issue 128 by analogc...@gmx.net: string routines
http://code.google.com/p/toped/issues/detail?id=128

better support for strings needed
(important for the handling of layer names, etc.)

the most generic approach would be to provide a function which could map a
string into a list and vice versa. like ..

int list lstr = str_to_list("something"); //converts into ASCII-code
string test = list_to_string ( {50,51,52,30} ); //ASCII-code to string

then it would be easy to manipulate the string with user-functions.

Another or additional approach would be to provide overloaded operators for
strings and/or special string functions like
strcmp, strncmp, strcat, strstr, etc. as defined in string.h

[to...@googlecode.com]

Issue 128: string routines
http://code.google.com/p/toped/issues/detail?id=128

This issue is now blocking issue 3.
See http://code.google.com/p/toped/issues/detail?id=3

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[to...@googlecode.com]

Updates:
Status: Accepted

Comment #2 on issue 128 by krustev...@gmail.com: string routines
http://code.google.com/p/toped/issues/detail?id=128

(No comment was entered for this change.)

[to...@googlecode.com]

Updates:
Labels: Component-Tell

Comment #4 on issue 128 by krustev....@gmail.com: string routines

http://code.google.com/p/toped/issues/detail?id=128

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[to...@googlecode.com]

Updates:
Status: Started

Comment #5 on issue 128 by krustev....@gmail.com: string routines
http://code.google.com/p/toped/issues/detail?id=128

Updates in r2446:
- Comparison operators ('==' and '!=') work now on strings
- Indexing works on strings now including as lvalue - i.e. replacement is
on. For example:
string a = "abcd";
echo(a[0]);
a[3] = "z";
a[1:2] = "xy";
// the a is now "axyz"

[to...@googlecode.com]

Comment #6 on issue 128 by krustev....@gmail.com: string routines
http://code.google.com/p/toped/issues/detail?id=128

All list specific operations work now for string:
Add/Insert/Append added in r2447
Delete/Reduce/Slice added in r2448

The major missing part is now search (and eventually replace).
I think regular expressions should be nice

[to...@googlecode.com]

Comment #7 on issue 128 by krustev....@gmail.com: string routines
http://code.google.com/p/toped/issues/detail?id=128

Regular expressions introduced in r2449

[to...@googlecode.com]

Comment #8 on issue 128 by krustev....@gmail.com: string routines
http://code.google.com/p/toped/issues/detail?id=128

The suggested ASCII conversion functions introduced in r2450.
str2uintl()
uintl2str()
Those must be documented.

[to...@googlecode.com]

Issue 128: string routines
http://code.google.com/p/toped/issues/detail?id=128

This issue is now blocking issue toped:177.
See http://code.google.com/p/toped/issues/detail?id=177

--

[to...@googlecode.com]

Updates:
Status: Fixed

Comment #10 on issue 128 by krustev....@gmail.com: string routines
http://code.google.com/p/toped/issues/detail?id=128

It looks to me we have enough powerful string manipulation routines now.

--

[to...@googlecode.com]

Updates:
Status: Verified

Comment #11 on issue 128 by krustev....@gmail.com: string routines
http://code.google.com/p/toped/issues/detail?id=128

(No comment was entered for this change.)