Re: another newbie question

new topic     » goto parent     » topic index » view thread      » older message » newer message

----- Original Message -----
From: Brian K. Broker <bkb at CNW.COM>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Monday, August 30, 1999 3:59 AM
Subject: Re: another newbie question


<snip>

> Can't help you here (not sure if I follow).  Rob?
>
> >So how do i specify to print the 2nd nested sequence?
>
> printf(1, "%s\n", { thisseq[nest2] } )  -- derived from your previous
> example

Given:
sentword = {"test1",{"test2","test3"}}

printf(1,"%s\n", sentword[1] )
-- prints: t

printf(1,"%s\n", {sentword[1]} )
-- prints: test1

printf(1,"%s\n", sentword[2] )
-- prints: test2

I have ordered an epiphany, and i hope it is delivered soon, so i can really
grasp exactly and fully all the implications of the preceeding and revel in
it, but for now, how do i avoid the following error msg with a test
preceeding the print statement?

printf(1,"%s\n", {sentword[2]} )
-- prints: sequence found inside character string

I don't know how many sequences are inside sentword[2] or how deep the
nesting may be inside sentword[2] (or inside sentword[2][3][6], etc). If i
must do extensive parsing of the {sentword} before i determine if a section
can be printed or sliced or added to, what is the advantage to nesting
sequences? And i cannot use sequence() to test with? It seems to me i need
another sequence (or another field inside {sentword}.) to record what in
{sentword} is a sequence and what is a nested sequence.

sentword = {{1,2},"test1",{{1,1,2},"test2","test3",{{1},"test4"}}}

Can i trap that Eu error msg and recover from it?

Kat,
foolishly trying to make it simple.
Or is it too simple already?

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu