Projects > Poasm

Poasm supported by Pelles C run-time library

(1/10) > >>

Vortex:
Here is a quick demo using the function _splitpath from Pelles C run-time static library crt.lib

_splitpath depends on the function strncpy which is extracted automatically from crt.lib



--- Code: ---include     splitpathDemo.inc

.data

path1       db 'D:\PellesC\project\splitpath.asm',0
f1          db 'drive = %s',13,10
            db 'dir   = %s',13,10
            db 'name  = %s',13,10
            db 'ext   = %s',13,10,0

.data?

buffer      db 128 dup(?)
drive1      db 4 dup(?)
dir1        db 32 dup(?)
name1       db 16 dup(?)
ext1        db 4 dup(?)

.code

start:

    invoke  _splitpath,ADDR path1,ADDR drive1,ADDR dir1,\
            ADDR name1,ADDR ext1

    invoke  wsprintf,ADDR buffer,ADDR f1,ADDR drive1,ADDR dir1,ADDR name1,\
            ADDR ext1

    invoke  StdOut,ADDR buffer
    invoke  ExitProcess,0

END start

--- End code ---

Adamanteus:
Annoying but actual - somebody could say to Pellec, that need support MASM in Pelles C IDE somehow  :icon_exclaim:

hutch--:
Trust me here, there is nothing wrong with POASM, its a very good tool. It has different macro notation to MASM but it does Intel spec assembler notation fine.

Vortex:
Hi Adamanteus,

No need to contact Pelle for this task. Follow the path :

Project -> Project Options -> Macros

Modify AS to reflect the path of ml.exe : \masm32\bin\ml.exe
Modify ASFLAGS to : /c /coff

Greenhorn:

--- Quote from: hutch-- on May 24, 2012, 04:15:37 AM ---Trust me here, there is nothing wrong with POASM, its a very good tool. It has different macro notation to MASM but it does Intel spec assembler notation fine.

--- End quote ---
I totally agree. POASM has a lot of nice features I wished MASM/JWASM would support.  ;)
But I think we get a little bit offtopic here.

Thanks for the example, Vortex.


Regards
Greenhorn

Navigation

[0] Message Index

[#] Next page