tiny-cobol-users

[Tiny-cobol-users] Question about current-date intrinsic function.

[Hudson R. <hud...@so...>]

hi all,

A user of TinyCOBOL brasilian mailing list reported the following problem:

When he run a shared library from a main program that contain the current-date intrinsic function, occurs a problem and shows the following message: 

>      "undefined symbol: tcob_intrinsic_current_date"

it uses the current-date function on the following way:

>      MOVE FUNCTION CURRENT-DATE(1:8) TO GDA-DATA

However, when I created a little program using the current date function and reference modification, the compiler shows errors. 
I searched for informations about reference modification in current-date intrinsic functions in COBOL 85 ISO/IEC draft, but I didn't find any reference about this. In our examples in test.code, I didn't find nothing too...

Could anyone tell me if the COBOL sentence above is according to the COBOL 85 standard and if there is any bug on TinyCOBOL?

I attach a little program to help..

Thanks 
Hudson

       identification division.
       program-id. currentdate.
       author. Hudson Reis.

       data division.
       working-storage section.
       01 wsDate.
          03 wsYear    pic 9(004) value zeros.
	  03 wsMonth   pic 9(002) value zeros.
	  03 wsDay     pic 9(002) value zeros.

       procedure division.
           move function current-date(1:8) to wsDate
      *>     move function current-date to wsDate
           display wsDate line 10 position 10
	   stop run.

Re: [Tiny-cobol-users] Question about current-date intrinsic function.

[Ferran P. <fer...@re...>]

I have programed all the intrinsic functions. I don't know if this is 
correct or not but  I'm sure that this don't work with TC.
Perharps in a future.

By now you can use temp variable to do this.

Hudson Reis wrote:

>hi all,
>
>A user of TinyCOBOL brasilian mailing list reported the following problem:
>
>When he run a shared library from a main program that contain the current-date intrinsic function, occurs a problem and shows the following message: 
>
>  
>
>>     "undefined symbol: tcob_intrinsic_current_date"
>>    
>>
>
>it uses the current-date function on the following way:
>
>  
>
>>     MOVE FUNCTION CURRENT-DATE(1:8) TO GDA-DATA
>>    
>>
>
>However, when I created a little program using the current date function and reference modification, the compiler shows errors. 
>I searched for informations about reference modification in current-date intrinsic functions in COBOL 85 ISO/IEC draft, but I didn't find any reference about this. In our examples in test.code, I didn't find nothing too...
>
>Could anyone tell me if the COBOL sentence above is according to the COBOL 85 standard and if there is any bug on TinyCOBOL?
>
>I attach a little program to help..
>
>Thanks 
>Hudson
>
>       identification division.
>       program-id. currentdate.
>       author. Hudson Reis.
>
>       data division.
>       working-storage section.
>       01 wsDate.
>          03 wsYear    pic 9(004) value zeros.
>	  03 wsMonth   pic 9(002) value zeros.
>	  03 wsDay     pic 9(002) value zeros.
>
>       procedure division.
>           move function current-date(1:8) to wsDate
>      *>     move function current-date to wsDate
>           display wsDate line 10 position 10
>	   stop run.
>  
>


-- 
Salutacions / Regards
+---------------------------------------------------------------+
| Ferran Pegueroles Forcadell                                   |
| mailto:fer...@re...                          |
| Tels (+34)937252106 - (+34)667658535                          |
| C/Unió 44 2n 2a 08201 Sabadell (BCN)                          |
+---------------------------------------------------------------+

Re: [Tiny-cobol-users] Question about current-date intrinsic function.

[Hudson R. <hud...@so...>]

Hi Ferran,

> I have programed all the intrinsic functions. I don't know if this is 
> correct or not but  I'm sure that this don't work with TC.
> Perharps in a future.

Ok, but I looked at ISO/IEC standard and it seems to be correct, however, I'll wait you update, thanks! :)

> By now you can use temp variable to do this.

Ok.

Thanks
Hudson