Re: trim(string) vs string.trim

Cor,
I'm not, nor was I ever disputing the fact that the Microsoft.VisualBasic
namespace is a part of the .net framework. I'll stand down on this
discussion now, it seems that we can agree to disagree on this subject.

Jared

"Cor Ligthert [MVP]" wrote:

Jared,

Who made the standards for the industry those six millions VB users ore the
fraction of that using C++ and Java. Strange enough needs those
programlanguages more books.The writters build have build around that their
theories, what for me only says something about the limited knowledge of
those writters. As your text was right, than there should be much more
semantic from VB in those languages.

An other main language is Cobol, a while ago it was still the most used
proffesional programming language I don't know if that is still the same.

http://www.levenez.com/lang/history.html#01

Beside that it seems that *we* are unable to make it clear to you. The
Microsoft.VisualBasic namespace is in Net the same as the System.Net.Data
namespace. It has only a name that not starts with System.Net. Maybe becomes
it clearer to do (although I doubt that), that everything using those is
simple in the resulting ils exe (assembly).

Just my thought reading your message

Cor

"Jared" <Jared@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:9899747E-443E-47BD-9589-260AB7316A1D@xxxxxxxxxxxxxxxx
I think you guys are taking me for someone who is advocating that all
should
use C#. I'm not trying to convert anyone, I simply stated that when
coding,
in whatever language you choose, one should try to conform to the
standards
the industry has put in place.

I can appreciate your frustration, as until recently I developed solely in
VB. I understand your points, and yes I know that I can use the
Microsoft.VisualBasic namespace in C# applications, I've never disputed
this,
nor was it ever the topic of discussion.

My points, with the exception of my backwards compatibility comment, are
language agnostic and follow the best practices laid out in books such as
Code Complete and Pragmatic Programmer. I simple stated that you should
use
a utility class and perform your trim there, even if you use the Trim
method
from the Microsoft.VisualBasic namespace and later I decide to convert it
I
only have to change it in a single location. This saves me from adding an
import/using statement to each and every object that is using the
Microsoft.VisualBasic Trim function. Isn't the goal to keep the class
closed
for modifications? Why go back and re-work numerous classes for such a
small
change?

On another similar issue:
Recently, I was working with a third party GIS mapping application. There
where few interfaces and/or they did not publicly expose some of the
internal
structures. We were tasked with interacting with the application's API to
perform search services through a web service interface. The problem
arose
when we found that we could not gain access to some of the properties
using
C#. Upon inspection of sample services gathered from the applications
creators we found they were using the late binding features of Visual
Basic
to perform nearly all of the operations. While this wasn't a huge
obstacle,
we were forced to use create a Visual Basic project to interact with the
application, either that or use reflection to instantiate internal/friend
classes of the framework.

This is the type of thing I'm trying to avoid in the future, the designers
of the application had the same mentality, it's easy enough to do using a
particular languages feature, why change the COM object, we can just
force
them to use Visual Basic or a more elaborate workaround.

I would love to hear you constructive comments on these subjects. Again,
try not to turn this into a language discussion.

Jared


"Jared" wrote:

Terry,
Please note before leaving your code in place that the Trim function is
implemented in the Microsoft.VisualBasic namespace for backward
compatability. If you use Reflector you'll find that the internal
implementation begins with the following check.

If ((str Is Nothing) OrElse (str.Length = 0)) Then
Return ""
End If

Now, I realize this call does the "work" for you, but, assume you (or
someone else)wants to convert the project to another .net language. C#
for
instance does not implement a global Trim() method. The developers
porting
your code are then forced** to change every reference to Trim() to either
a
utility function or to the native framework methods. It's best to just
conform and avoid the backward compatible functions.


** The conversion utility may make this change for you.

"Terry Olsen" wrote:

Yes, after all the input, I have decided to leave it as
String=Trim(String)

"Branco Medeiros" <branco.medeiros@xxxxxxxxx> wrote in message
news:1156188881.224330.253450@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Terry Olsen wrote:
I have an app that makes decisions based on string content. I need
to
make
sure that a string does not contain only spaces or newlines. I am
using
the
syntax 'Trim(String)" and it works fine. I thought I'd change it to
the
VB
.NET method "String.Trim" but that throws an object exception.

Which brings the question: is it compliant to use Trim(String), or
is it
more within etiquette to use If Not String Is Nothing Then
String.Trim?

The advantage of using Trim instead of String.Trim is exactly that
Trim
will recognize when a String is Nothing and return "" as a result. If
this is the logic of your application, then instead of doing:

If SomeStr Is Nothing then
Value = ""
'I personally preffer Value = String.Empty
Else
Value = String.Trim
End If

you could spare the effort and just use Value = Trim(SomeStr)

On the other hand, if you must know when a passed string is invalid
(Nothing) then probably checking for Nothing before calling
String.Trim
is the way to go.

Regards,

Branco.







.

Relevant Pages

  • Re: trim(string) vs string.trim
    ... programlanguages more books.The writters build have build around that their ... proffesional programming language I don't know if that is still the same. ... Microsoft.VisualBasic namespace is in Net the same as the System.Net.Data ... a utility class and perform your trim there, even if you use the Trim ...
    (microsoft.public.dotnet.languages.vb)
  • Re: use-package & name conflict: why they are not deferred?
    ... introduces its own namespace. ... Try doing that in some other language! ... (print (foo-a foo) ... right here you also seem to be confusing structs and classes. ...
    (comp.lang.lisp)
  • Re: Help: I cannot selectNodes with a simple XPath expression
    ... current namespace context other than a QName, ... About the best thing I can say about XML and all the bastard children ... of the eXtremely Messed-up Language is that it is better than LDAP. ... problems are definitely not due to Tcl, ...
    (comp.lang.tcl)
  • Re: trim(string) vs string.trim
    ... in whatever language you choose, one should try to conform to the standards ... a utility class and perform your trim there, even if you use the Trim method ... Please note before leaving your code in place that the Trim function is ... more within etiquette to use If Not String Is Nothing Then String.Trim? ...
    (microsoft.public.dotnet.languages.vb)
  • Re: the jargon lisp1 vs lisp2 [was: function aliasing]
    ... namespace" or "having a particular finite number of namespaces" is ... I somewhat agree, but human language tends to be a living thing, ... Mac-like or PC-like is, and consequently it's hard to know if Unix-like ... creative use of English itself, and I see no problem with that. ...
    (comp.lang.lisp)