Mercurial > cgi-bin > hgwebdir.cgi > VMS > VMS_Implementations > VMS_impls > VMS__MC_shared_impl

comparison VMS.c @ 52:f59cfa31a579

find changesets by author, revision, files, or words in the commit message
fixed up probes just a bit
author Me
date Sat, 30 Oct 2010 21:53:55 -0700
parents 8f7141a9272e
children 42dd44df1bb0 420a09d3f32a
comparison
equal deleted inserted replaced
21:e38566a22f76 22:0c3bd2780395
547 /* This is for OS requests and VMS infrastructure requests, such as to create 547 /* This is for OS requests and VMS infrastructure requests, such as to create
548 * a probe -- a probe is inside the heart of VMS-core, it's not part of any 548 * a probe -- a probe is inside the heart of VMS-core, it's not part of any
549 * language -- but it's also a semantic thing that's triggered from and used 549 * language -- but it's also a semantic thing that's triggered from and used
550 * in the application.. so it crosses abstractions.. so, need some special 550 * in the application.. so it crosses abstractions.. so, need some special
551 * pattern here for handling such requests. 551 * pattern here for handling such requests.
552 * Doing this just like it were a second language sharing VMS-core.
553 *
552 * This is called from the language's request handler when it sees a request 554 * This is called from the language's request handler when it sees a request
553 * of type VMSSemReq 555 * of type VMSSemReq
556 *
557 * TODO: Later change this, to give probes their own separate plugin & have
558 * VMS-core steer the request to appropriate plugin
559 * Do the same for OS calls -- look later at it..
554 */ 560 */
555 void inline 561 void inline
556 VMS__handle_VMSSemReq( VMSReqst *req, VirtProcr *requestingPr, void *semEnv, 562 VMS__handle_VMSSemReq( VMSReqst *req, VirtProcr *requestingPr, void *semEnv,
557 ResumePrFnPtr resumePrFnPtr ) 563 ResumePrFnPtr resumePrFnPtr )
558 { VMSSemReq *semReq; 564 { VMSSemReq *semReq;