/media/bill/PROJECTS/Qnial/code development/strings - chrs_before_after_str_i_test.txt


*************************
22May2018 11:07  


qnial> chrs_before_after_str_i_test
 
# chr_before_after_subStr_test  example 1 vrp :  OK - result matches standard
t_input, t_standard, t_result = 
+-+--+--------------------------------------------------+
|1|-1|Bi(r,v,t) =  q/c*(vrp)/rs^3  =  (v/c)E0(r,t)|
+-+--+--------------------------------------------------+
B
B
All should be OK including the "?address" result, which is caused by 69 being accepted (0 <= i) but is out of 

range of tell gage shape t_input
 
# chr_before_after_subStr_test  example 1 vrp :  OK - result matches standard
t_input, t_standard, t_result = 
+--+--+--------------------------------------------------+
|-1|50|Bi(r,v,t) =  q/c*(vrp)/rs^3  =  (v/c)E0(r,t)|
+--+--+--------------------------------------------------+
)
)
All should be OK including the "?address" result, which is caused by 69 being accepted (0 <= i) but is out of 

range of tell gage shape t_input
 
# chrs_before_after_str_i_test  example 2 r :  FAILED - result does NOT match standard
t_input, t_standard, t_result = 
+-+--+---------------------------------------------------------+
|1|10|e^2*(r·b)*r(rb)/|r2 - r1|^2*6*Bpe^2*Bep^2*(-3/2/π|
+-+--+---------------------------------------------------------+

?op_parameter ?op_parameter ?op_parameter
All should be OK including the "?address" result, which is caused by 69 being accepted (0 <= i) but is out of 

range of tell gage shape t_input
 
# chrs_before_after_str_i_test  example 3 ∂/ :  FAILED - result does NOT match standard
t_input, t_standard, t_result = 
+-+--+------------------------------------------------------------------------------------------+
|1|-2|[·dl : E(r´,t´)]  = -1/c*dp[dt : [dA : B(r,t)  •n]] .and.[·dl : E(r´,t´)]|
+-+--+------------------------------------------------------------------------------------------+
fault
?op_parameter ?op_parameter ?op_parameter
All should be OK including the "?address" result, which is caused by 69 being accepted (0 <= i) but is out of 

range of tell gage shape t_input
 
# chrs_before_after_str_i_test  example 4 :  FAILED - result does NOT match standard
t_input, t_standard, t_result = 
+--+--+----------+------------------------------------------------------------------+
|-1|67|Ei(rp,t)·|r/r/sinO *[  ∂/∂O(sinO*Ei(rp,t)·Pp) - ∂/∂P(Ei(rp,t)·O|
+--+--+----------+------------------------------------------------------------------+
O
?op_parameter ?op_parameter ?op_parameter ?op_parameter
All should be OK including the "?address" result, which is caused by 69 being accepted (0 <= i) but is out of 

range of tell gage shape t_input
>> OK - a bit of bug and changes to explanations


qnial> chrs_before_after_str_i_test
#+-----+
chrs_before_after_str_i_test, Tue May 22 12:53:59 2018
 
# chr_before_after_subStr_test  example 1 vrp :  OK - result matches standard
t_input, t_standard, t_result = 
+-+--+--------------------------------------------------+
|1|-1|Bi(r,v,t) =  q/c*(vrp)/rs^3  =  (v/c)E0(r,t)|
+-+--+--------------------------------------------------+
B
B
 
# chr_before_after_subStr_test  example 1a vrp :  OK - result matches standard
t_input, t_standard, t_result = 
+--+--+--------------------------------------------------+
|-1|50|Bi(r,v,t) =  q/c*(vrp)/rs^3  =  (v/c)E0(r,t)|
+--+--+--------------------------------------------------+
)
)
 
# chrs_before_after_str_i_test  example 2 r :  OK - result matches standard
t_input, t_standard, t_result = 
+-+--+---------------------------------------------------------+
|1|11|e^2*(r·b)*r(rb)/|r2 - r1|^2*6*Bpe^2*Bep^2*(-3/2/π|
+-+--+---------------------------------------------------------+


should be OK, reading unicode. Keep in mind that "·" adds one extra i_str!!
 
# chrs_before_after_str_i_test  example 2a r :  OK - result matches standard
t_input, t_standard, t_result = 
+-+--+---------------------------------------------------------+
|1|13|e^2*(r·b)*r(rb)/|r2 - r1|^2*6*Bpe^2*Bep^2*(-3/2/π|
+-+--+---------------------------------------------------------+
�
�
gives single-byte unicode, as it starts one byte within a unicode "" (-18 -124 -87), i_start = 12
 
# chrs_before_after_str_i_test  example 2b r :  OK - result matches standard
t_input, t_standard, t_result = 
+--+--+---------------------------------------------------------+
|-1|15|e^2*(r·b)*r(rb)/|r2 - r1|^2*6*Bpe^2*Bep^2*(-3/2/π|
+--+--+---------------------------------------------------------+


should be OK, reading prior to a unicode  "" i_end = 14
 
# chrs_before_after_str_i_test  example 3 ∂/ :  OK - result matches standard
t_input, t_standard, t_result = 
+-+--+------------------------------------------------------------------------------------------+
|1|-2|[·dl : E(r´,t´)]  = -1/c*dp[dt : [dA : B(r,t)  •n]] .and.[·dl : E(r´,t´)]|
+-+--+------------------------------------------------------------------------------------------+
?address
?address
This tests an out-of-bound i_str: -2, giving negative indices and error 
 
# chrs_before_after_str_i_test  example 4 :  OK - result matches standard
t_input, t_standard, t_result = 
+--+--+------------------------------------------------------------------+
|-1|67|r/r/sinO *[  ∂/∂O(sinO*Ei(rp,t)·Pp) - ∂/∂P(Ei(rp,t)·O|
+--+--+------------------------------------------------------------------+
?address
?address
This tests an out-of-bound i_str: 67, > len: 66

>> OK, seems good!!









# enddoc