C# - from VB to C (and from old to new C) puzzles

Replies to This Discussion

Permalink Reply by Giulio Piacentino on August 19, 2014 at 6:20am

Hi Peter

I took the time to go one script after the other and I fixed all typo's, a couple of errors in the automatic code translation, and a missed conversion to doubles (rather than integers) that was causing issues.

It should all be working now. If not everything is perfect yet, just watch a little more for similar things :)
I hope this helps,

Giulio
--
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com

Attachments:

• fixes.gh, 30 KB

Permalink Reply by peter fotiadis on August 19, 2014 at 7:14am

Hi Giulio

I wonder...what was the most embarrassing? (maybe Case2 - I supposed that the double declaration means that the integer division (if on) should been overridden).

Thanks a lot

best, Peter

Permalink Reply by Giulio Piacentino on August 19, 2014 at 8:54am

Nothing was embarrassing, at all. I do all these mistakes myself -- that's why I am a bit faster at spotting them now.

Giulio
--
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com

Permalink Reply by peter fotiadis on August 20, 2014 at 7:24am

Nothing you said? Well ... THAT'S embarrassing, he he:

That @$#$@ Surface.PointAt (Ux, Vx) - double, double again:

If I define iun,ivn (i,j,uNum,vNum are integers) as :

double iun = i / uNum;
double ivn = j/ vNum;

the results are like the Case2 (expected)

If I define them as (a "bit" ridiculous):

double iun = (i + 0.0) / (uNum + 0.0);
double ivn = (j + 0.0) / (vNum + 0.0);

the results are OK.

Thus the embarrassing question of the day: how to do it with a less ridiculous (int.ToDouble is not a method) way? And why double test = (Convert.ToDouble(i) / Convert.ToDouble(uNum)) doesn't work?

BTW: this works:

best, Peter