DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

+ Reply to Thread
Page 1 of 3 1 2 3 LastLast
Results 1 to 15 of 33

Thread: YES.

  1. #1
    Bill McCarthy Guest

    YES.

    Reply to this post to vote for :

    To adopt the CLR naming rules for the integer types. The CLR defines Int16,
    Int32 and Int64. The VB code editor will rename Long to Int32 and Integer to
    Int16, or alternatively the compiler will generate a non-fatal warning to remind
    you to chanage Long to Int32 and Integer to Int16.



  2. #2
    Michael \(michka\) Kaplan Guest

    Re: YES.

    YES.

    --
    MichKa

    a new book on internationalization in VB at
    http://www.i18nWithVB.com/




  3. #3
    Bill McCarthy Guest

    Re: YES.

    Yes, of course <g>




  4. #4
    Simon Fell Guest

    Re: YES.

    On Thu, 26 Oct 2000 15:12:10 +1100, "Bill McCarthy"
    <Bill_McC@iprimus.com.au> wrote:

    >Reply to this post to vote for :
    >
    > To adopt the CLR naming rules for the integer types. The CLR defines Int16,
    >Int32 and Int64. The VB code editor will rename Long to Int32 and Integer to
    >Int16, or alternatively the compiler will generate a non-fatal warning to remind
    >you to chanage Long to Int32 and Integer to Int16.
    >



    --
    Simon
    www.4s4c.com

  5. #5
    Mike Riley Guest

    Re: YES.

    YES. This solution causes *zero* problems for any of the other .net
    languages. It will scale painlessly into the future (if we ever need an
    int128). It will also prevent the problems with accidentally converting old
    code more than once, and pasting old code into a new project

    -Mike



  6. #6
    Tom Shelton Guest

    Re: YES.

    You betcha.



  7. #7
    Bob O`Bob Guest

    Re: YES.

    Bill McCarthy wrote:

    "voting" in this kind of forum does not seem to me to be useful.

    If votes meant anything, those of us raising ANY kinds of concerns
    over VB.Net would have been voted out of the newsgroup by the cheerleaders
    weeks ago.

    I don't think it's even arguable that the universally acclaimed changes
    outnumber the ones that have fostered disagreement. There's LOADS of
    stuff they got right the first time.



    Bob O`Bob
    --
    Watch for my new book, "Just The Only Complete Dummy's Hardcore Fast Track Pure
    Teach Yourself Guide to Mastering Advanced Essential Core Hands-On Step-by-Step
    Unleashed in 24 Hours, Special Edition, Gold, You'll ever Need Bible"

  8. #8
    Mike Henshaw Guest

    Re: YES.


    "Bill McCarthy" <Bill_McC@iprimus.com.au> wrote in message
    news:39f7acd4@news.devx.com...
    > Reply to this post to vote for :
    >
    > To adopt the CLR naming rules for the integer types. The CLR defines

    Int16,
    > Int32 and Int64. The VB code editor will rename Long to Int32 and Integer

    to
    > Int16, or alternatively the compiler will generate a non-fatal warning to

    remind
    > you to chanage Long to Int32 and Integer to Int16.
    >
    >




  9. #9
    Carlos J. Quintero Guest

    Re: YES.

    Yes.

    "Bill McCarthy" <Bill_McC@iprimus.com.au> escribió en el mensaje
    news:39f7acd4@news.devx.com...
    > Reply to this post to vote for :
    >
    > To adopt the CLR naming rules for the integer types. The CLR defines

    Int16,
    > Int32 and Int64. The VB code editor will rename Long to Int32 and Integer

    to
    > Int16, or alternatively the compiler will generate a non-fatal warning to

    remind
    > you to chanage Long to Int32 and Integer to Int16.
    >
    >




  10. #10
    Larry Triezenberg Guest

    Re: YES.

    Yes


  11. #11
    Dan Rhea Guest

    Re: YES.

    Here's to hoping this will have an effect... <grin></grin>
    ___________________________
    Dan Rhea - Mailto:danr@sirs.com
    Windows CD-ROM Programmer
    SIRS Mandarin, Inc.
    (561) 994-0079 x757
    "Bill McCarthy" <Bill_McC@iprimus.com.au> wrote in message
    news:39f7acd4@news.devx.com...
    > Reply to this post to vote for :
    >
    > To adopt the CLR naming rules for the integer types. The CLR defines

    Int16,
    > Int32 and Int64. The VB code editor will rename Long to Int32 and Integer

    to
    > Int16, or alternatively the compiler will generate a non-fatal warning to

    remind
    > you to chanage Long to Int32 and Integer to Int16.
    >
    >




  12. #12
    Bob Butler Guest

    Re: YES.


    "Bill McCarthy" <Bill_McC@iprimus.com.au> wrote in message
    news:39f7acd4@news.devx.com...
    > Reply to this post to vote for :
    >
    > To adopt the CLR naming rules for the integer types. The CLR defines

    Int16,
    > Int32 and Int64. The VB code editor will rename Long to Int32 and Integer

    to
    > Int16, or alternatively the compiler will generate a non-fatal warning to

    remind
    > you to chanage Long to Int32 and Integer to Int16.
    >


    Yes, unambiguous, easily extendible,... although I do not see a need for the
    compiler warning.




  13. #13
    Paul Marshall Guest

    Re: YES.



    --
    Paul Marshall
    pmarshal@vulcraft-al.com

  14. #14
    Craig Clearman Guest

    Re: YES.

    Hi Bill,

    Sed quis custodiet ipsos custodes?

    Ciao, Craig


  15. #15
    Greg Longtin Guest

    Re: YES.




Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


Top DevX Stories

Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL


Sponsored Links