netdev - using C99 in nasm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090628181915.GB19425@lenovo>
Date:	Sun, 28 Jun 2009 22:19:15 +0400
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	NKML <netdev@...r.kernel.org>
Subject: using C99 in nasm

Hi,

is there a special reason why don't we
use C99 style of assignment for structure members?

For exmaple when assign ofmt structure members
why don't use positional independing fashion
like

struct ofmt of_macho = {
	.fullname	= "NeXTstep/OpenStep/Rhapsody/Darwin/MacOS X object files",
	.shortname	= "macho",
	.helpstring	= NULL,
	.debug_formats	= null_debug_arr,
	...
};

For the sake of portability maybe?

	-- Cyrill
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html