help2002

It's UWAweek 47

help2002

This forum is provided to promote discussion amongst students enrolled in CITS2002 Systems Programming.
Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!" followup message.

Displaying the 7 articles in this topic

Showing 7 of 828 articles.
Currently 89 other people reading this forum.

UWA week 38 (2nd semester, week 8) ↓

1st project about Command-Line Arguments (arg0, arg1, etc.) in Program Execution" (all 7)

9:37pm Wed 18th Sep, Jinseok K.

I don't really understand what 'the variables arg0, arg1, and so on, provide access to the program's command-line arguments which provide real-valued numbers' means. I would appreciate it if someone could explain what this means. Thank you

1st project about Command-Line Arguments (arg0, arg1, etc.) in Program Execution" (all 7)

9:14am Thu 19th Sep, Jinseok K.

i know the what is the mean arg0, arg1... but i couldn't get it "provide access to the program's command-line arguments which provide real-valued numbers' means." here.

1st project about Command-Line Arguments (arg0, arg1, etc.) in Program Execution" (all 7)

1:13pm Thu 19th Sep, Xiaoqin F.

I asked other student, we guess they should be a reference of parameter for generated C translation files, you can define like this char* arg0=argv[1] in your c file, and the generated c file can use arg0 directly

1st project about Command-Line Arguments (arg0, arg1, etc.) in Program Execution" (all 7)

3:44pm Thu 19th Sep, Jinseok K.

Thank you!

1st project about Command-Line Arguments (arg0, arg1, etc.) in Program Execution" (all 7)

10:26pm Thu 19th Sep, Joshua N.

"Xiaoqin Fan" <24*5*5*9@s*u*e*t*u*a*e*u*a*> wrote:

> I asked other student, we guess they should be a reference of parameter for generated C translation files, you can define like this char* arg0=argv[1] in your c file, and the generated c file can use arg0 directly

Just make sure to convert argv[1] to a double.

1st project about Command-Line Arguments (arg0, arg1, etc.) in Program Execution" (all 7)

9:23am Fri 20th Sep, Jinseok K.

"Joshua Noble" <22*6*9*8@s*u*e*t*u*a*e*u*a*> wrote:

> "Xiaoqin Fan" <24*5*5*9@s*u*e*t*u*a*e*u*a*> wrote: > > > I asked other student, we guess they should be a reference of parameter for generated C translation files, you can define like this char* arg0=argv[1] in your c file, and the generated c file can use arg0 directly > > Just make sure to convert argv[1] to a double.

I wonder after converting a argv[1] to a double ex> argv[1] = 123.ml Is this 123 assigned to the variable like "x <- 123.0" ? thank you

1st project about Command-Line Arguments (arg0, arg1, etc.) in Program Execution" (all 7)

9:53am Fri 20th Sep, Joshua N.

"Jinseok Kim" <24*3*9*7@s*u*e*t*u*a*e*u*a*> wrote:

> "Joshua Noble" <22*6*9*8@s*u*e*t*u*a*e*u*a*> wrote: > > > "Xiaoqin Fan" <24*5*5*9@s*u*e*t*u*a*e*u*a*> wrote: > > > > > I asked other student, we guess they should be a reference of parameter for generated C translation files, you can define like this char* arg0=argv[1] in your c file, and the generated c file can use arg0 directly > > > > Just make sure to convert argv[1] to a double. > > > I wonder after converting a argv[1] to a double > > ex> argv[1] = 123.ml > > Is this 123 assigned to the variable like "x <- 123.0" ? > > thank you

I don't think you completely understand how argument passing works in ml. Have you read these posts? [help2002]⬈ [help2002]⬈