search for: 60dde0

Displaying 2 results from an estimated 2 matches for "60dde0".

Did you mean: 60dd70
2016 May 20
2
identical on closures
...70 02 LISTSXP g0c0 [MARK] TAG: @60dd70 01 SYMSXP g0c0 [MARK,LCK,gp=0x4000] "srcref" (has value) @15a65d8 19 VECSXP g0c1 [MARK] (len=1, tl=0) @10f3dd0 13 INTSXP g0c3 [OBJ,MARK,ATT] (len=8, tl=0) 1,15,1,15,15,... ATTRIB: @cc9618 02 LISTSXP g0c0 [MARK] TAG: @60dde0 01 SYMSXP g0c0 [MARK,NAM(2),LCK,gp=0x4000] *"srcfile" *(has value) *@cc97d8* 04 *ENVSXP* g0c0 [OBJ,MARK,NAM(2),ATT] <0xcc97d8> @cca8a8 03 CLOSXP g0c0 [MARK,NAM(2),ATT] FORMALS: @604b58 00 NILSXP g0c0 [MARK,NAM(2)] BODY: @cc9eb8 06 LANGSXP g0c0 [MARK,ATT] @604998...
2016 May 20
2
identical on closures
I'm confused by this: > identical(function() {}, function() {}) [1] FALSE Yet, after loading the Matrix package (which redefines det), the following is checked (in library.checkConflicts): > identical(get("det", baseenv()), get("det", asNamespace("Matrix")), ignore.environment=T) [1] TRUE I've looked at the code in identical.c and for closures it