# config empty lists
**URL:** https://community.zeek.org/t/config-empty-lists/19
**Category:** Zeek
**Created:** [September 18, 1998, 3:01am UTC](https://community.zeek.org/t/config-empty-lists/19 "1998-09-18T03:01:07Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Vern](https://community.zeek.org/u/Vern)
#### Post date: [September 18, 1998, 3:01am UTC](https://community.zeek.org/t/config-empty-lists/19/1 "1998-09-18T03:01:07Z")
[back from travel and now catching up on email]
> In the runtime configs, fresh out of the tarball, there are several
> lists (eg, const ``NFS\_world\_servers = { ... }'' in portmapper.bro)
> that I don't wish to have any elements. I may eventually want to
> use these, as I grow more experienced with BRO and want to refine
> my usage of it, but at the moment, I have no use for this list.
>
> By removing the elements, and leaving an empty ``{ }'' (in perl-
> style), I see messages like ``error: parse error, at or near "}"'' .
>
> Is my only alternative to remove all references to this list in
> the files?
You can change the definitions to:
global NFS\_world\_servers: addr;
You need to give a type since previously Bro was inferring it from the
initialization list, but without any initializers it can't do this; and you
need to make it "global" because Bro is unhappy with a "const" that's not
initialized (I should probably change this).
Vern
---
### Author:  [@system](https://community.zeek.org/u/system)
#### Post date: [May 6, 2022, 3:36pm UTC](https://community.zeek.org/t/config-empty-lists/19/2 "2022-05-06T15:36:03Z")