PHP 8.4.1 Released!

    fdf_get_value

    (PHP 4, PHP 5 < 5.3.0, PECL fdf SVN)

    fdf_get_value — フィールドの値を得る

    説明

    fdf_get_value(resource $fdf_document, string $fieldname, int $which = -1): mixed

    指定したフィールドの値を取得します。

    パラメータ

    fdf_document

    fdf_create()、 fdf_open() あるいは fdf_open_string() が返す FDF ドキュメントハンドル。

    fieldname

    FDF フィールドの名前を表す文字列。

    which

    このオプションパラメータを渡すことで、配列フィールドの 要素が取得可能です。番号はゼロから始まります。配列以外のフィールドでは、 このオプションは無視されます。

    戻り値

    フィールドの値を返します。

    参考

    Improve This Page

    Learn How To Improve This Page • Submit a Pull Request • Report a Bug
    ＋add a note

    User Contributed Notes 1 note

    up
    0
    mclinden at informed dot net
    22 years ago
    (i filed a bug report/feature request for this on bugs.php.net and assigned it to myself hartmut@php.net)

    The default behavior for the FDF Toolkit is to return an FDFErcNoValue for the FDFGetValue when the field exists but has no value.

    Whether or not this is truly an error is debateable. It seems to become an issue in documents created by Acrobat 5 when optional fields are included in a form with required fields since the default behavior seems to be to populate the HTTP_FDF_DATA with the results of the FDFNextFieldName enumerator, which would include the fields which have no value.

    This would not be a problem except that the PHP function fdf_get_value() does not specifically test for the FDFErcNoValue condition but, instead, tests for the more general FDFErcOK. If this value is not the result of the error code, the system issues warnings (the display of which could be turned off), but the broader question is, should this be a warning condition at all?

    Put another way, should a return of FDFErcNoValue for FDFGetValue be considered an event worth generating a warning?
    ＋add a note
    To Top