Wrox Programmer Forums
|
BOOK: ASP.NET 2.0 Website Programming Problem Design Solution ISBN: 978-0-7645-8464-0
This is the forum to discuss the Wrox book ASP.NET 2.0 Website Programming: Problem - Design - Solution by Marco Bellinaso; ISBN: 9780764584640
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: ASP.NET 2.0 Website Programming Problem Design Solution ISBN: 978-0-7645-8464-0 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old January 28th, 2007, 02:16 AM
Authorized User
 
Join Date: Jan 2007
Posts: 63
Thanks: 0
Thanked 0 Times in 0 Posts
Default why use base[] indexers??

I'm a little new to C#, so maybe there is a good reason as to why Marco is using base["member"] indexers instead of just using base.member? Or even, this.member? I'm particularly talking about when uses it on page 101 Chapter 3 for the custom configuration section class.

If one of the two other options I mentioned are equivalent, I don't think it's a good idea to get members via a string look-up like that, since you can easily misspell them (which actually happened by the way--it's in the errata for the book).
 
Old January 31st, 2007, 12:50 AM
Authorized User
 
Join Date: Jan 2007
Posts: 63
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Can anybody answer this? I'm having a hard time finding an answer...






Similar Threads
Thread Thread Starter Forum Replies Last Post
Base Folder RNedel ASP.NET 2.0 Basics 2 September 5th, 2007 04:33 PM
d.base MathLearner VB Databases Basics 1 May 17th, 2007 07:39 AM
Indexers and Properties pagates C# 5 March 15th, 2005 08:08 AM
Indexers with c# kobystud C# 2 May 28th, 2004 09:52 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.