Comments on: Manage Parameters

By: Unlimited Timer « Gallimaufry

Unlimited Timer « Gallimaufry — Wed, 09 Jun 2010 02:16:21 +0000

[...] from my library. I have described two of them – param and param.get – already in the post Manage Parameters. The third – param.delete – is used to remove a parameter from the parameter [...]

By: Arnold Kegebein

Arnold Kegebein — Wed, 24 Jun 2009 17:18:24 +0000

@Mikhail
Thank you for the links. I knew about them already. And as you can see in my newest entry, I consider you and your blog as an inspiration for my ideas working with parameters.

I was working with an Evaluate/Quote solution myself, but were running in some problems too. But I am using evaluation in other CFs, because it can make life so much easier.

I wonder, what you think about my other functions. I am on vacation right now, using the time to add some content to my blog. Expect more from my Custom Function Vault soon.

By: More Fun with Parameters – Gallimaufry

More Fun with Parameters – Gallimaufry — Wed, 24 Jun 2009 17:04:16 +0000

[...] my previous entry I described two customs functions for managing parameters: param and param.get. They encode and [...]

By: Mikhail_Edoshin

Mikhail_Edoshin — Wed, 24 Jun 2009 08:31:57 +0000

I ended up with a similar suite of functions (http://edoshin.skeletonkey.com/2006/02/options.html) (I even used circumflex for the same reason but I like your variant more, because in the wrapped form it is more readable than mine.

There’s also a similar solution somewhere in SixFriedRice blog (http://sixfriedrice.com/wp/blog/)

By the way, technically there’s more FileMaker-native way to first Quote() a string and then Evaluate() it. E.g. the param wrapper like that would be:

Quote( List( Quote(key), Quote(value) ) )

and then a similar sequence of Evaluate() steps to fetch a value by a key. It looks that this variant can be made type-aware, but when I test this I get weird results. Besides, this variant loses text formatting, while the Substitute-based one does not.