When using a material event for storing the view- and project-matrix, they may lag one frame behind.

Example:
material mat1 {..} // uses stored matrices
material mat2 {..} // stores matrices of view2
view view1 {..} // shows an entity with mat1
view view2 {..} // shows an entity with mat2
view view3 {..} // rendered last, for not allowing you to say "use matView/matProj in mat1"

If view2 is rendered after view1, the matrices used are from the previous frame.

None the less, functions like get_viewMatrix(view*), get_projMatrix(view*) or get_worldMatrix(entity*) would make sense. I guess the matrices are "precalculated" and stored inside the objects anyway.