X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=date:from:to:subject:message-id:mail-followup-to:references
	:mime-version:content-disposition:content-transfer-encoding
	:in-reply-to:user-agent;
	bh=Q6n6GOXtuhfU2CWOkIN8ZuyxwG8AZjQL6P+epcIXhj8=;
	b=j1CLxrq/2prtoew0w6DfT/6y3femIn6cCq6r07DCH6YtGsYi41QbHROwcVzFtXoeob
	d/ZPykPRDxmy1TEucbufDZUz859dCrGGCmvGudT44ZE2vv3dLo20NoO3r/lmrX2Cv61p
	nFVxdPAgVaaNkwopFLoZLfu8RmER4V3jE6CVSramycYrBdoTC6mVqPCl0HdPIcQkrdGN
	Heo96cNDQKoHDSfi8cAiZyV8jb85MkBEwIRXRjSca2WratOR+iKpx3ZSIKx6ENMWRwDJ
	YvkzXH3j1d8J+HXz3Lkxzs++PVcUyCxd6Rlr3t+UPrwME982J48VihkHdZZZSDUxL67t
	EGAw==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to
	:references:mime-version:content-disposition
	:content-transfer-encoding:in-reply-to:user-agent;
	bh=Q6n6GOXtuhfU2CWOkIN8ZuyxwG8AZjQL6P+epcIXhj8=;
	b=YTpwozaGb1visrJ6jTwFaQGrMuZ3egLM5z1MPSxzNtTOT9els76/n/U0/AehpjHGdU
	71HBHX1QteWGBVdbPNjxXcdV9qkQkb4Veu7tcUCVwMeTae7cZaRjfI2amWQCMBKj/xW8
	WdI6NTiriO7IZILU6I+HVtu+YwdYjxrSQRtf8U2kBBTuasJgWf0c4lrFYBiOrcoIB80q
	q/dhDzoEr8GSkDaFeWs/dKUNhdicWAQh2maA0nRZYWJdfBoS4uwE7EBt61RnIvUUpfxf
	2nKwqLOPfGdGSNEGoiXEUKvf2Q2PqCCVWBSoBQRP3rmipttNVg4Mrxa4iMvOrQpYBlqc
	L4ZA==
X-Gm-Message-State:	AE9vXwO4mJmAxcJkaRSgYZmWQazjcp72pa9tAp+mRIBB7tVW43Z9Q0j/NUIOxooeUEMWGA==
X-Received:	by 10.25.155.145 with SMTP id d139mr1367826lfe.120.1472065100796;
	Wed, 24 Aug 2016 11:58:20 -0700 (PDT)
Date:	Wed, 24 Aug 2016 21:58:18 +0300
From:	"Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user <geda-user AT delorie DOT com>
Subject:	Re: [geda-user] Can an attribute be attached to text for later
	inclusion in gnetlist backend?
Message-ID:	<20160824185818.GD14293@localhost.localdomain>
Mail-Followup-To:	geda-user <geda-user AT delorie DOT com>
References:	<CAGde_xMkqgbbfH81MPOLPfTaui0wRvmUctk31r-eE3=fQ+U0pA AT mail DOT gmail DOT com>
	<A9C29BBE-B381-4BD1-BD54-E0E27DF1307C AT noqsi DOT com>
	<20160823053301 DOT 865f671a1b40b5a422e59ce7 AT gmail DOT com>
	<da433c1d-c711-e0d8-f9ff-a6e843bfe266 AT sbcglobal DOT net>
	<AB0B2DAD-9075-4AEC-B33E-A57DA050B079 AT noqsi DOT com>
	<CAGde_xOYrkv-4eWyR4OOTT+XQMPcr4MxmT1xomB9uCneZBCT6A AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CAGde_xOYrkv-4eWyR4OOTT+XQMPcr4MxmT1xomB9uCneZBCT6A@mail.gmail.com>
User-Agent:	Mutt/1.5.23 (2014-03-12)
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, Aug 24, 2016 at 11:47:45AM +0200, Svenn Are Bjerkem (svenn DOT bjerkem AT googlemail DOT com) [via geda-user AT delorie DOT com] wrote:
> On 24 August 2016 at 03:24, John Doty <jpd AT noqsi DOT com> wrote:
> > I believe what Svenn wants is a “toplevel” attribute, not attached to a symbol, like the spice-epilog attribute here:
> >
> > Of course, your gnetlist back end needs the code to make sense of such a thing.
> 
> Indeed. I want a toplevel attribute for the VHDL prolog.
> The original vhdl backend has this hard-coded, and I would like to
> augment my backend with the opportunity to set this on a per-schematic
> base to override the default, if user wants to define his own.
>

Hi Svenn,

What backend are you using, vhdl or vams?

If vhdl, the only change needed is to change
vhdl:write-context-clause e.g. as follows:

(define (vhdl:write-context-clause)
  (let ((prolog (gnetlist:get-toplevel-attribute "vhdl-prolog")))
    (format #t
            (if (string=? prolog "not found")
                "-- Context clause
library IEEE
use IEEE.Std_Logic_1164.all;
"
                prolog))))

The same could be done for vams. If this works for you, I could
commit such changes. The only thing we have to discuss before is
the prolog attribute name conventions.

Of course, you might your own backend for personal use. However,
if such a change is useful for you and harmless for others, why to
not have it?

-- 
  Vladimir

- Raw text -