 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : PicoMite V6.01.00 release candidates
  Page 18 of 18 |
|||||
| Author | Message | ||||
| toml_12953 Guru  Joined: 13/02/2015 Location: United StatesPosts: 498 |
I found out why my results are only 67.7% on the regex test. On my RC17 calculator, p$="\d" ? p$ \d but on my RC19 calculator, p$="\d" ? p$ d The newer version is dropping the backslash from strings. Any ideas? Edited 2025-11-24 11:36 by toml_12953 Footnote added 2025-11-24 12:45 by toml_12953 Solved! I had OPTION ESCAPE in my library so whenever I started a program it interpreted strings differently. Once I removed that, the tests ran with a 100% pass rate. |
||||
| ville56 Senior Member  Joined: 08/06/2022 Location: AustriaPosts: 295 |
I found a strange behavior with the EXECUTE command: the following code uses a sub with a string parameter to execute the string. If the sub is CALLED from an EXECUTE statement the string length seems to induce strange behavior. OPTION EXPLICIT OPTION DEFAULT NONE option escape 'activate special characters in strings 'test for nesting exeute statements do_exec("print \qnow in 1st level\q") 'execute print from 1st level of sub do_exec("nest_2nd") 'nest to second level by "execute nest_2nd" end sub nest_2nd 'now in second level of "execute" command do_exec("print \q2nd\q") 'print 3 char string -> success do_exec("print \qL2:456\q") 'print 6 char string -> success, this is the max length (8 inluding the 2 quotes) do_exec("print \qL2:4567\q") 'print 7 chars -> fail end sub sub nest_3rd do_exec("print \q3rd\q") 'print 3 char string -> success do_exec("print \qL3:1234567\q") do_exec("nest_4th") end end sub sub nest_4th do_exec("print \q4th\q") 'print 3 char string -> success do_exec("print \qL4:1234567\q") end sub sub do_exec(uar as string) print "----- execute begin print "cmd to execute: ";uar 'print out string to be executed execute uar 'execute user-action-routine print "----- execute end" end sub ' Result is: > run ----- execute begin cmd to execute: print "now in 1st level" now in 1st level ----- execute end ----- execute begin cmd to execute: nest_2nd ----- execute begin cmd to execute: print "2nd" 2nd ----- execute end ----- execute begin cmd to execute: print "L2:456" L2:456 ----- execute end [33 Execute uar 'execute user-action-routine Error : Invalid character: 6 > So the code crashes after "do_exec("print \qL2:4567\q")" but seems to jump somehow into the middle of the "sub do_exec(...)" without any reason. It cannot have used the regular call mechanism, otherwise the "print "----- execute begin" must have been executed, which it did not. Maybe there is something wrong on the execution stack when executing the EXECUTE command in this constellation. The behavior also changes when the code is changed, e.g. more print statements for debugging or changeing the length of the strings to be printed with execute. Are there any know limitations (except the ones described in the manual) with EXECUTE or is this a bug? Gerald 73 de OE1HGA, Gerald |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10653 |
You can't execute from within an execute if that is what you are doing |
||||
| ville56 Senior Member Joined: 08/06/2022 Location: AustriaPosts: 295 |
That was my intention ... 73 de OE1HGA, Gerald |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10653 |
V6.01.00RC20 PicoMiteV6.01.00RC20.zip Reset the image size in the build making more space available on the A: drive in most cases Make regular expression processing compatible with OPTION ESCAPE Changes MID$ command so the length to be replaced can be 0 - i.e. insert the new string at the position specified New commands: LMID(array%(),start [,num])=string$ inserts string$ into the longstring array%() at position start replacing num existing characters. If num isn't specified then it is calculated from the length of string$. num can be 0 in which case string$ is inserted at the position specified. Note how MID$ and LMID together with INSTR and LINSTR can be used effectively to edit text   REDIM [PRESERVE] array(dimensions) This resizes the array specified with the dimensions given. If the optional sub-command PRESERVE is specified the existing data will be copied into the new array. The new array can be bigger or smaller than the original. In the case of string arrays the original LENGTH specified is preserved. Note that for multi-dimensional arrays only the last dimension can be changed if PRESERVE is used. DIM a%(99,9) REDIM PRESERVE a%(99,19) 'OK REDIM PRESERVE a%(199,9) 'ERROR |
||||
| toml_12953 Guru Joined: 13/02/2015 Location: United StatesPosts: 498 |
Not on my setup. When I delete OPTION ESCAPE from my library, I get 100% success from regex.bas but when I add OPTION ESCAPE back in, I only get 63.7% success. |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10653 |
That because of the way the tests are written. The string with the escape sequence is read into a variable with option escape on - nothing I can do about that. However, if you create the string with the correct characters or use a string literal then the regex will work whereas it didn't before. e.g test 31 fails but ? instr("test123","\d",size) works as does s$="\\d":? instr("test123",s$,size) |
||||
| toml_12953 Guru Joined: 13/02/2015 Location: United StatesPosts: 498 |
With RC19 and RC20 GP0 and GP1 don't work for COM1: anymore. GP4 and GP5 still work for COM2: though. PicoMite MMBasic RP2350B V6.01.00RC20 OPTION SERIAL CONSOLE COM1,GP0,GP1,BOTH OPTION SYSTEM SPI GP10,GP11,GP12 OPTION SYSTEM I2C GP6,GP7, SLOW OPTION FLASH SIZE 16777216 OPTION LIBRARY_FLASH_SIZE 50000 OPTION COLOURCODE ON OPTION CONTINUATION LINES ON OPTION CASE UPPER OPTION DEFAULT COLOURS GREEN, BLACK OPTION KEYBOARD I2C OPTION PICO OFF OPTION CPUSPEED (KHz) 360000 OPTION LCDPANEL CONSOLE ,, FF00,, 20 OPTION DISPLAY 26, 40 OPTION LCDPANEL ST7796SP, PORTRAIT,GP14,GP15,GP13,,INVERT OPTION LCD BACKLIGHT 20 OPTION SDCARD GP17, GP18, GP19, GP16 OPTION AUDIO GP26,GP27', ON PWM CHANNEL 5 OPTION PLATFORM PicoCalc OPTION PSRAM PIN GP47 Edited 2025-11-26 14:34 by toml_12953 |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10653 |
Works for me. Sorry but there is no way I can diagnose a build you are doing with modifications to the source that then doesn't work. I would you suggest you start with my release and do an option reset. and then set OPTION SERIAL CONSOLE GP0,GP1,B That definitely works on a rp2350B. If that doesn't work you have a HW issue. If is does then you have an issue with your build  |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10653 |
V6.01.00RC21 PicoMiteV6.01.00RC21.zip Edit enhancements: The in-built editor is very useful and personally I use it most of the time rather than using a PC based approach. Two things have always irritated me though: first, having to use shift-F3 to repeat a search and second, no replace function. I was musing on this in bed as you do (sad I know  ) when I realised that with a particular approach it should be easy to implement replace functionality without risking the stability of the editor so RC21 contains the editor enhancements as follows:You can now use SHIFT-F3, ctrl-G, OR F6 to get the next match If you then use SHIFT-F5, ctrl-I or F8 the system will replace the search target string with the contents of the paste buffer. That works but requires you to have copied something into the paste buffer using the usual F4/F5 mechanism So, having just done a search using F3 etc. you can now press SHIFT-F4, ctrl-F, or F7 and this will open a dialog allowing you to directly enter a string into the paste buffer and on pressing return, replace the search target string. This is much simpler than that explanation made it seem. Suppose you want to replace every occurrence of GP0 with GP6 then you can proceed as follows: F3 - enter GP0 'define the search target and find the first occurrence F7 - enter GP6 'define the replacement string and do the first replacement repeat until you get a not found message F6 ' find next F8 ' replace next end repeat Edited 2025-11-27 20:57 by matherp |
||||
| Page 18 of 18 |
|||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
