World: r3wp

BrianH, correct except not, I think, parens:
>> foreach word [(1 + 2)][print mold word]
(1 + 2)

That's interesting. Parens and paths used to be active - oh yeah, 
that was changeda while ago. Still, there are some value types that 
are active (function types, lit-path, lit-word) and if you think 
you will get one of these you should disable their evaluation by 
referencing them with a get-word, unless you intend them to be evaluated.

parens changed at around View 1.2.10

both parens and paths changed between  View 1.2.1 and 1.2.5, actually.

Gordon: I did not read this thread in a whole but as for converting 
CSV string to/from Rebol blocks, here is some fully functionnal functions 
:

;***** Conversion function from/to CSV format
csv-to-block: func [

 "Convert a string of CSV formated data to a Rebol block. First line 
 is header."
	csv-data [string!] "CSV data."

 /separator separ [char!] "Separator to use if different of comma 
 (,)."
	/without-header "Do not include header in the result."

 /local out line start end this-string header record value data chars 
 spaces chars-but-space

 ; CSV format information http://www.creativyst.com/Doc/Articles/CSV/CSV01.htm
] [
	out: copy []
	separ: any [separ #","]
	

 ; This function handle replacement of dual double-quote by quote 
 while copying substring
	this-string: func [s e] [replace/all copy/part s e {""} {"}]
	; CSV parsing rules

 header: [(line: copy []) value any [separ value] (if not without-header 
 [append/only out line])]

 record: [(line: copy []) value any [separ value] (append/only out 
 line)]

 value: [any spaces data any spaces (append line this-string start 
 end)]

 data: [start: some chars-but-space end: | #"^"" start: any [some 
 chars | {""} | #"," | newline] end: #"^""]
	chars: complement charset rejoin [ {"} separ newline]
	spaces: charset exclude { ^-} form separ
	chars-but-space: exclude chars spaces
	
	parse/all csv-data [header any [newline record] any newline end]
	out
]

block-to-csv: func [
	"Convert a block of blocks to a CSV formated string." 
	blk-data [block!] "block of data to convert"
	/separator separ "Separator to use if different of comma (,)."
	/local out csv-string record value v
] [
	out: copy ""
	separ: any [separ #","]
	; This function convert a string to a CSV formated one

 csv-string: func [val] [head insert next copy {""} replace/all copy 
 val {"} {""} ]
	record: [into [some [value (append out #",")]]]

 value: [set v string! (append out csv-string v) | set v any-type! 
 (append out form v)]
	

 parse/all blk-data [any [record (remove back tail out append out 
 newline)]]
	out
]

there's also the sql csv thingy in the library

DideC: Thanks.  I've copied and pasted it for review and added it 
to my local public library.  This script should be useful especially 
with the html help page.   Documentation on a script is very rare 
and much appreciated.


Graham: Did a search using  "librarian" and search term of  "sql 
cvs" and didn't come up with anything.  Although, I think we've got 
it covered now anyhow.

Trying to do some macro expansion in text ...

This is not working :(

expand-macros: func [tmp [string!] macros [block!]
	/local white-rule rule len lexp
] [
	white-rule: charset [#" " #"^/"]
	foreach [macro expansion] macros [
        len: length? macro
		lexp: length? expansion
		rule:  compose/deep copy [

            [ to here: white-rule (macro) white-rule ( change/part here expansion 
            len  ?? macro) lexp skip ]
            to end
        ]
		parse/all tmp [some [rule]]
	]
	tmp
]

Are macros marked by some starting character? That would make this 
easier to implement.

Also, it would help to know whether macro expansions can contain 
further macros.

no, they can be any characters (alphanumeric), but should not contain 
further macros.

ise if the macros are delimited you should be able to do it in one 
pass

What I was trying to do above is to look for the macro text preceded 
by a space or newline, and ending in a space or newline.

and then replace in situ.

leaving the whitespace unaffected.

in that case sorting them from long to short to begin with will foil 
recursive macro rxpansion

at  the macros and expansons single tokens

HTML/XML entities begin with & and end with ; for just this reason. 
What kind of text? can you give us an example?

well, the macros wiill end up being delimited by whitespace

Heart: Heart regular rate and rhythm, no rubs, murmurs, or gallops 
noted. 

A: Abdomen:  soft, nontender, no mass, no hernia, no guarding, no 
rebound tenderness, no ascites, non obese 
Hbp Hypertension (high blood pressure) #401.9.  
Ii Type II Diabetes #250.00

Are macros the only thing delimited by whitespace?

So, someone might type

heart:
A: with striae

macros are typed inside normal text.

That A: isn't delimited by whitespace.

it is .. it's preceded by a newline character

from the line above ...

Not it it were on the first line. Plus, is the : part of the macro?

True .. not if it were on the first line.  Some macros contain punctuation.

so, a: is a macro, whereas "a" is not.

the macros are user defined.

so, in the examples given above, the first word in each line is the 
macro.

Do they always contain the same punctuation, is the punctuation per-macro, 
of does it need to be factored out?

isn't there a controled vocabulary for this sort of thing

per macro.

Is a macro always the first word in a line?

what do you mean controlled vocabulary?

no, it can be anywhere in a line.

an ontology

Is there a seperate syntax for defining macros?

no, it's just a text file which is read in at start up.

the scenario is this guy uses these macros as he types up his notes. 
 his software currently expands them inline as he types.

So in use, a macro a: will always be a: in the text. Will it be A: 
sometimes, or "a:"?

I would have to intercept the keyboard handler to do this .. so I 
want to try and just do the replacement after he's finished typing.

macros won't be case sensitive.

but groups of people doing the sane thing dont use the same nacros? 
  they should

no, they don't use the same macros.

so, it's user specific.

personal shorthand

yes