Assem Medhat
Assem Medhat
This issue needs to be labled 'SNAP'. may you label it @Pranavchiku . I think if we handled this issue we can proceed with compiling dealloc.f90 The unhandled expception in...
> @Pranavchiku I explored the way to implement this according to your suggestion. I think it will be achieved using the `fill_array_details_()` function. #4111 opened by @assem2002 uses this same...
@kmr-srbh. Yeah you're right about your suggested code.but we should be able to call an external function that's defined in another file using `external` keyword. gfortran compiles [these files ](https://github.com/lfortran/lfortran/issues/4008#issue-2299271520)...
@kmr-srbh ```shell assem@assem-PC:~/Desktop/fortran/test_05$ gfortran -c func.f90 assem@assem-PC:~/Desktop/fortran/test_05$ gfortran -c prog.f90 assem@assem-PC:~/Desktop/fortran/test_05$ gfortran -o mmm func.o prog.o assem@assem-PC:~/Desktop/fortran/test_05$ ./mmm 9 ``` I think it just compiles `prog.f90` and the object file...
as @Pranavchiku mentioned it would compile normally with `--generate-object-code` flag. `-c` flag in gfortran handles this issue with no problem. should we do the same in LFortran? If not just...
Insights from #2257 ### String as Primitive type to the front end language It's either you're dealing with a language that has a string type as primitive (like Fortran and...
**FixedSizeString** : - Its size is known at compile time and allocated as an array in the back end. - allocated on the stack as user intended. - No need...
Do we need an error reference test here?
for the given example : ```fortran TYPE test_type2 integer :: num END TYPE test_type2 TYPE test_type1 integer :: num integer :: arr_1(3) type(test_type2):: arr_2(3) END TYPE test_type1 TYPE(test_type1), DIMENSION(5) ::...