>The point of naming the wildcard "theURL" was to have the string
>matching the wildcard put into a variable with that name. An
>alternative would be a function as you suggest (I like
>wildcardChunk(1) and wildcardText(-1) best). It was my mistake to
>suggest a new chunk type "the first found chunk" or to name that
>function "foundChunk".
Ruediger,
that's what I thought, too. I just thought it was more natural to refer to
a string that'll end up in a variable as "string varName" and to a string
we don't care about simply as "a string".
>"expression" would be a reserved word, you can't name your variables
>"expression" or "or". So that is not a problem, but I don't think it
>is necessary to add the keyword "expression" to each "or". I think if
>you need a boolean expression, you can place them in brackets:
True, but leaving away "expression" after "find" and in various other
places will kill existing syntax like 'find "string"'. That's why we
absolutely need the first "expression". I'd also like to make it easier to
tell apart a boolean "or" or an expression "or". I think this'll ease
parsing a bit for the compiler. We might also want a short form for
expression, like expr.
Reserved words are not present in all xTalks (MetaCard is very strict
about most of these, but HC and SC are much more forgiving in this regard)
and thus I think it's still an issue which needs to be considered (though
here it can be neglected because usually one wouldn't name a boolean
variable "expression".
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
