Re: IEEE 1364-2005 Encryption draft with consensus changes

From: Shalom.Bresticker@freescale.com
Date: Mon Jan 17 2005 - 23:20:48 PST

  • Next message: Shalom.Bresticker@freescale.com: "Re: SystemVerilog (P1800) and Verilog (P1364) Draft Documents Available"

    I had to go down to 7.6 pt font size to get it on one line, instead of the
    regular 10 pt size.

    It would help if some of the strings in the line could be shortened or if
    the optional exit or match arguments could be omitted.

    In looking at this, though, I found the following syntax in 28.3.29
    (now 28.4.29):

    runtime_license=(library=<string>, entry=<string>, feature=<string>, [ exit=<string>,] [ match=<number> ] )

    Two problems I see here:

    1. The syntax says that the 'feature' argument is required, but it does not appear in the example.

    2. The argument shows feature=<string> and 'exit=<string>' ending with commas even if not followed by anything.
    Should it have been

    runtime_license = ( library = <string> , entry = <string>, feature = <string> [ , exit = <string> , ] [ , match = <number> ] )

    with the comma appearing only if the following optional argument appears
    (with spaces to show that white space is permitted) ?

    Thanks,
    Shalom

    On Tue, 18 Jan 2005 Shalom.Bresticker@freescale.com wrote:

    > Verilog allows arbitrarily long lines.
    > This is just a problem of the LRM.
    > I'll try reducing the font size.
    >
    > I do agree that in the future it would be nice to allow multi-line directives.
    >
    > Shalom
    >
    >
    > On Mon, 17 Jan 2005, Steven J. Dovich wrote:
    >
    > > > I have a problem with the example line
    > > >
    > > > `pragma protect runtime_license=(library="libsecret.so", entry="chklic", exit
    > > > ="rlslic", match=42)
    > > >
    > > > This is a single line which is too long for the page, so it wraps around,
    > > > then it looks like two lines, but that is wrong, because you can't have
    > > > a two line compiler directive, except for `define, but this directive has
    > > > to be one line because it is all part of a single directive and all
    > > > compiler directives have to be one line as far as I remember, in contrast
    > > > to regular source text.
    > > >
    > > > Or do I remember wrong?
    > > >
    > > > Suggestions?
    > >
    > > You remember correctly. We need to bring some of the `define definition
    > > into the `pragma specification, to permit backslash continuation of lines.
    > > That will allow you to render in the line length constraints of the
    > > text. The capability is useful in its own right, so we won't be
    > > introducing requirements for the sole purpose of avoiding layout
    > > problems in the text.
    > >
    > > I will plan to discuss this at the Wednesday meeting.
    > >
    > > /sjd
    > >
    >
    > 

    -- 
Shalom Bresticker                        Shalom.Bresticker @freescale.com
Design & Verification Methodology                    Tel: +972 9  9522268
Freescale Semiconductor Israel, Ltd.                 Fax: +972 9  9522890
POB 2208, Herzlia 46120, ISRAEL                     Cell: +972 50 5441478
  
[ ]Freescale Internal Use Only      [ ]Freescale Confidential Proprietary

    This archive was generated by hypermail 2.1.4 : Mon Jan 17 2005 - 23:04:23 PST and
    sponsored by Boyd Technology, Inc.