[Expat-discuss] Expat-discuss Digest, Vol 69, Issue 1

[Rahim @ Easy Devices.co.uk]

Hello ,
Please tell me the complete solution of using 
1.php_domxml.dll 
and 
2.How to extract the xml file from website using a php function.

Please reply as soon as it is possible.
Thanks for yours replies. Sorry to bother u all.

Thanks once again


Thanks
 
Best regards,

Abdul Rahim Khan

Computer Engineer
Easy Devices.co.uk

Tel: 0871 7000 156
Fax: 0871 7000 159

Mobile : 00447733355291
Web: www.easydevices.co.uk
Email: rahim at easydevices.co.uk



-----Original Message-----
From: expat-discuss-bounces at libexpat.org
[mailto:expat-discuss-bounces at libexpat.org] On Behalf Of
expat-discuss-request at libexpat.org
Sent: 01 December 2005 11:00
To: expat-discuss at libexpat.org
Subject: Expat-discuss Digest, Vol 69, Issue 1

Send Expat-discuss mailing list submissions to
	expat-discuss at libexpat.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://mail.libexpat.org/mailman/listinfo/expat-discuss
or, via email, send a message with subject or body 'help' to
	expat-discuss-request at libexpat.org

You can reach the person managing the list at
	expat-discuss-owner at libexpat.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Expat-discuss digest..."


Today's Topics:

   1. Re: 64 bit integers in Expat 2.0? (Nick MacDonald)


----------------------------------------------------------------------

Message: 1
Date: Wed, 30 Nov 2005 09:30:30 -0500
From: Nick MacDonald <nickmacd at gmail.com>
Subject: Re: [Expat-discuss] 64 bit integers in Expat 2.0?
To: expat-discuss at libexpat.org
Message-ID:
	<bdcd32c90511300630v51fb2711u4939b89133f57fc4 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Well... not that the Windows API should stand as a stunning example of
clarity, but I believe they have two entries for a lot of functions (I
believe they nest, but not sure as I don't spend much time writing
non-portable code for specific OSes)... one for Unicode and one for
non-Unicode.

Maybe you combine two ideas...  have function names provide the return type
and optionally only include one set of names or the other depending on some
build flag.  That way old code doesn't break, new code can use the new
functions, and eventually you could mark the old function names as
deprecated.  Since the problem you face is technically only in one
direction, you could remove the old function names in favour of new function
names, and optionally include a macro to "rename" the new functions so they
still appear present for old code.

And maybe I'm just babbling... being that I have never used those particular
API functions anyway...  ;-)


On 11/29/05, Karl Waclawek <karl at waclawek.net> wrote:
>
> Yes, that might be an option as well.
> It just doesn't feel "right" for me to add four new alternative API 
> members when the original ones aren't used that often. API bloat?
>


------------------------------

_______________________________________________
Expat-discuss mailing list
Expat-discuss at libexpat.org
http://mail.libexpat.org/mailman/listinfo/expat-discuss


End of Expat-discuss Digest, Vol 69, Issue 1
********************************************