Holger Reif wrote:
>
> 2.) The user is a developer.
> 2a.) He has MASM. Perhaps he don't want to install another assembler.
> 2b.) He hasn't MASM installed.
> Is it possible to deliver consistent versions of MASM/NASM files?
> Or should we just develop two separate versions. This seems
> acceptable since these asm parts are quite stable to my mind.
>
Well a developer need not have MSDN professional membership. He might
just have purchased VC++ and doesn't have the option to install MASM or
doesn't want to download a huge file or various other reasons.
The MASM/NASM assembly language files are auto generated from the same
perl "source" script so maintaining them shouldn't be a problem: the
NASM stuff was mainly just a case of adding another "flavour" to the
perl assembly language generator. We can zap all the Win32 asm files now
as well.
Steve.
--
Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED]
Senior crypto engineer, Celo Communications: http://www.celocom.com/
Core developer of the OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
