Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #8133

Re: Visual Studio Vulcan.Net Unknown Type

Message-ID <5560796A.2000408@heliks.nl> (permalink)
Date 2015-05-23 14:58 +0200
Newsgroups comp.lang.clipper.visual-objects
From Robert van der Hulst <robert@heliks.nl>
Subject Re: Visual Studio Vulcan.Net Unknown Type
References <9d689b10-0ee8-4d5f-b28e-20192081c87d@googlegroups.com> <mjnhuh$8p2$1@news.albasani.net> <555F7706.9080906@heliks.nl> <mjopeo$r66$1@news.albasani.net>

Show all headers | View raw


Jamal,

I don't think Vulcan is confusing at all.
This makes perfect sense to me:

System.DateTime.DaysInMonth(2015, 2):ToString()

The first part of the expression is:

System.DateTime.DaysInMonth(2015, 2)

This is the same in Vulcan as C# because DaysInMonth is a static method 
on the System.DateTime  structure ( like a function in the 
System.DateTime namespace). The return value of this method is a number.

The second part of the expression is

<number>:ToString()

ToString() is a method that you are calling on the numeric result of the 
DaysInMonth() function.

I personally think C# and VB are confusing, because they are using the 
dot operator for too many things.

And I do not think that Vulcan should be saved from VO semantics. The VO 
semantics in probably the only justification for existence of Vulcan. In 
many other aspects it is much better to use C# and/or VB.

Robert


>
> I thought I tried that with : operator. I tried again and it worked. 
> Anyway, the intellisense still does not work!
> What's worse is the Vulcan compiler confusing error message:
> 'System.DateTime.now' : unknown type (are you missing an assembly 
> reference?)
>
> It should probably say, "hey, you did not use the : to call a static 
> method."
>
> I think the Vulcan way is confusing especially if you are used to C# 
> or VB.NET.
>
> Let's take System.DateTime.DaysInMonth(2015, 2) in C# or VB.NET. 
> DaysInMonth(int,int) is a method, yet in Vulcan, you also write 
> System.DateTime.DaysInMonth(2015, 2). It is basically the same.
> To return a string in C# you write System.DateTime.DaysInMonth(2015, 
> 2).ToString()
> In Vulcan, you write: System.DateTime.DaysInMonth(2015, 2):ToString()
>
> Talk about confusion!!
>
> I think it is time to save Vulcan from VO semantics and do it the .NET 
> way! Which is the standard way!


-- 
Robert van der Hulst
robert@heliks.nl

Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Visual Studio Vulcan.Net Unknown Type Gary <gkeefe109@gmail.com> - 2015-05-22 07:37 -0700
  Re: Visual Studio Vulcan.Net Unknown Type "Jamal Assaf" <someone@example.com> - 2015-05-22 11:28 -0400
    Re: Visual Studio Vulcan.Net Unknown Type Robert van der Hulst <robert@heliks.nl> - 2015-05-22 20:35 +0200
      Re: Visual Studio Vulcan.Net Unknown Type "Jamal Assaf" <someone@example.com> - 2015-05-22 22:42 -0400
        Re: Visual Studio Vulcan.Net Unknown Type Robert van der Hulst <robert@heliks.nl> - 2015-05-23 14:58 +0200
      Re: Visual Studio Vulcan.Net Unknown Type Gary <gkeefe109@gmail.com> - 2015-05-29 08:30 -0700

csiph-web