[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4762: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3897)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4764: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3897)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4765: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3897)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4766: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3897)
newlispfanclub.alh.net • View topic - newLISP Development Release v.10.6.3

newLISP Development Release v.10.6.3

Notices and updates

newLISP Development Release v.10.6.3

Postby Lutz » Wed Jul 08, 2015 3:23 pm

This development release adds new functionality to existing functions and fixes bugs.

Files and release notes: http://www.newlisp.org/downloads

Thanks to everybody participating in this release. Special thanks to Kosh, who did most of the work for the Windows 64-bit release.
Lutz
 
Posts: 5279
Joined: Thu Sep 26, 2002 4:45 pm
Location: Pasadena, California

Re: newLISP Development Release v.10.6.3

Postby HPW » Wed Jul 08, 2015 5:05 pm

Hello,

Thanks Lutz for the ongoing development.

Unfourtunatly my Norton Internet Security delete the windows installers because it reports WS.Reputation.1

But Virustotal scans without problem:

https://www.virustotal.com/de/file/590f ... 436374630/

https://www.virustotal.com/de/file/2c9b ... 436374825/

I will report a false positiv.

Regards
HPW
 
Posts: 1376
Joined: Thu Sep 26, 2002 9:15 am
Location: Germany

Re: newLISP Development Release v.10.6.3

Postby HPW » Wed Jul 08, 2015 6:10 pm

Hello,

In my regular testing against my neobook demo app, I get a error with commands which get imported into the newlsip.dll (32 bit). They now throw a access violation in my (Turtle3:run).

Until 10.602 all run without problems.

I noticed a different DLL-size from 10602 to 10603:
301.568 Bytes
286.734 Bytes

Any changes how Dll-callbacks were done?

The following command throws the violation:
(hpwImageTextOut "RImage1" "Dragon Fractal" "380" "70" "Times" "12" "clWhite" "clNavy")

> hpwImageTextOut
(lambda (nbpara1 nbpara2 nbpara3 nbpara4 nbpara5 nbpara6 nbpara7 nbpara8) (hpwImageExec
"" "9" nbpara1 nbpara2 nbpara3 nbpara4 nbpara5 nbpara6 nbpara7 nbpara8))

> hpwImageExec
hpwImageExec@2D814CC

hpwImageExec is the imported command from the neobook dll.

Regards
HPW
 
Posts: 1376
Joined: Thu Sep 26, 2002 9:15 am
Location: Germany

Re: newLISP Development Release v.10.6.3

Postby rickyboy » Wed Jul 08, 2015 7:16 pm

(λx. x x) (λx. x x)
rickyboy
 
Posts: 595
Joined: Fri Apr 08, 2005 7:13 pm
Location: Front Royal, Virginia

Re: newLISP Development Release v.10.6.3

Postby Lutz » Wed Jul 08, 2015 9:06 pm

Since the new development v.10.6.3, a newer development systems with GCC version 4.9.2 from the TDM system is used and running on Windows 7. Before v.10.6.3, Windows newLISP development was on Windows XP. It was time to move on to Windows 7 as a minimum, to take advantage of 64-bit Windows.

This is how simple ffi and extended ffi 'import' and 'callback' are tested:

newlisp-10.6.3/qa-specifif-tests/qa-libffi : simple and extended ffi for callbacks and imports
newlisp-10.6.3/qa-specifif-tests/qa-libc-libffi : extended ffi only and using system libraries
newlisp-10.6.3/examples/opengl-demo.lsp : simple ffi and callback 32-bit only
newlisp-10.6.3/examples/opengl-demo-ffi.lsp : extended ffi and callback 32-bit and 64-bit (UNIX only)

specifically for Windows 32-bit, great example how to work with various Windows DLLs:

newlisp-10.6.3/examples/win32demo.lsp : simple ffi only and with callbacks

When importing self compiled libs on Windows and using the simple ffi, try importing with “cdecl”. See these changes in the qa-libffi file from v10.6.2 to v10.6.3. Try also the extended ffi, present on all Windows versions and all shipped installers for OSX and Linux. Also, the extended ffi does not need to specify “cdecl” versus using the default stdcall on Windows.
Lutz
 
Posts: 5279
Joined: Thu Sep 26, 2002 4:45 pm
Location: Pasadena, California

Re: newLISP Development Release v.10.6.3

Postby HPW » Thu Jul 09, 2015 5:51 am

Hello,

The exported function hpwImageExec is compiled with stdcall-option.
It has worked for years now with the newlisp.dll
I have also other exported functions with stdcall which still works with 10603.

I have to further investigate where the access vioaltion occurs.


Regards
HPW
 
Posts: 1376
Joined: Thu Sep 26, 2002 9:15 am
Location: Germany

Re: newLISP Development Release v.10.6.3

Postby HPW » Thu Jul 09, 2015 7:30 am

HPW
 
Posts: 1376
Joined: Thu Sep 26, 2002 9:15 am
Location: Germany

Re: newLISP Development Release v.10.6.3

Postby HPW » Thu Jul 09, 2015 8:14 am

Hello,

Looking with the dependency walker at both DLL, I noticed that 10603 has the WEP-entry point as the first entry where it was the last in 10602.

And there is a new newLispLibConsole.
What to do with it in DLL?

Regards
HPW
 
Posts: 1376
Joined: Thu Sep 26, 2002 9:15 am
Location: Germany

Re: newLISP Development Release v.10.6.3

Postby HPW » Thu Jul 09, 2015 9:18 am

Hello,

I finally figured it out:

DLL < 10603 were tolerant when calling the function with less parameter than defined.

FUNCTION hpwImageExec( password,cmdid,Params0,Params1,Params2,Params3,Params4,Params5,Params6,Params7,Params8,Params9 : PChar ) : BOOLEAN; stdcall;

So adding an empty param solves the exception:

(hpwImageExec "" "3" "RImage1" "0" "0" "100" "100" "clRed" "" "psSolid" "2" "")

Regards
HPW
 
Posts: 1376
Joined: Thu Sep 26, 2002 9:15 am
Location: Germany

Re: newLISP Development Release v.10.6.3

Postby HPW » Thu Jul 09, 2015 12:43 pm

HPW
 
Posts: 1376
Joined: Thu Sep 26, 2002 9:15 am
Location: Germany

Re: newLISP Development Release v.10.6.3

Postby Lutz » Thu Jul 09, 2015 3:05 pm

Thanks Hans-Peter for bringing this to Symantec's attention.
Lutz
 
Posts: 5279
Joined: Thu Sep 26, 2002 4:45 pm
Location: Pasadena, California

Re: newLISP Development Release v.10.6.3

Postby HPW » Sat Jul 11, 2015 6:06 am

HPW
 
Posts: 1376
Joined: Thu Sep 26, 2002 9:15 am
Location: Germany

Re: newLISP Development Release v.10.6.3

Postby Lutz » Sat Jul 11, 2015 1:04 pm

Only installs in the newLISP program directory.

Corrected here: http://www.newlisp.org/downloads/CodePa ... tml#toc-24
and here: http://www.newlisp.org/downloads/develo ... tml#toc-24
Lutz
 
Posts: 5279
Joined: Thu Sep 26, 2002 4:45 pm
Location: Pasadena, California

Re: newLISP Development Release v.10.6.3

Postby xytroxon » Sun Jul 12, 2015 6:38 am

"Many computers can print only capital letters, so we shall not use lowercase letters."
-- Let's Talk Lisp (c) 1976
xytroxon
 
Posts: 296
Joined: Tue Nov 06, 2007 3:59 pm

Re: newLISP Development Release v.10.6.3

Postby Lutz » Sun Jul 12, 2015 1:29 pm

This was already changed: http://www.newlisp.org/downloads/develo ... terns.html showing 10.6.3 in the title page.

Perhaps you where looking in the version for 10.6.2 in the main download directory. It also has a current date, but does not have the "Win32" -> "Windows" update. I will keep both versions updated till the next stable release, but in a version sensitive manner.
Lutz
 
Posts: 5279
Joined: Thu Sep 26, 2002 4:45 pm
Location: Pasadena, California

Re: newLISP Development Release v.10.6.3

Postby kosh » Mon Jul 13, 2015 9:06 pm

kosh
 
Posts: 69
Joined: Sun Sep 13, 2009 5:38 am
Location: Japan

Re: newLISP Development Release v.10.6.3

Postby Lutz » Mon Jul 13, 2015 10:18 pm

Thanks for the configure-alt fix. It works now, but on a Windows 7 64-bit systems it also compiles a 32-bit newlisp.exe and without libffi using the TDM GCC 64 toolset.

I am not too concerned about this, as we have working Windows 32/64-bit compilations using the normal configure script and the TDM GCC 64 toolset. It can use the mingw64 to compile 32-bit newlisp.exe with libffi without any error messages. using make winall or make winall64, the executables for the Windows installers are done together with DLLs.

The configure-alt file is getting old and I wonder if it still should be included in the final 10.6.4 release? Perhaps Ted W. has some time to update the Windows portion, or we simply take the Windows portion out and use it only for Unix. It would also be nice to have a working libffi detection on many Unix platforms.
Lutz
 
Posts: 5279
Joined: Thu Sep 26, 2002 4:45 pm
Location: Pasadena, California

Re: newLISP Development Release v.10.6.3

Postby johu » Thu Jul 16, 2015 8:40 am

johu
 
Posts: 143
Joined: Mon Feb 08, 2010 8:47 am

Re: newLISP Development Release v.10.6.3

Postby Lutz » Thu Jul 16, 2015 4:04 pm

Many thanks, Johu. Updates are here:

http://www.newlisp.org/downloads/develo ... nprogress/
Lutz
 
Posts: 5279
Joined: Thu Sep 26, 2002 4:45 pm
Location: Pasadena, California

Re: newLISP Development Release v.10.6.3

Postby TedWalther » Fri Jul 17, 2015 7:39 pm

Cavemen in bearskins invaded the ivory towers of Artificial Intelligence. Nine months later, they left with a baby named newLISP. The women of the ivory towers wept and wailed. "Abomination!" they cried.
TedWalther
 
Posts: 605
Joined: Mon Feb 05, 2007 1:04 am
Location: Abbotsford, BC

Re: newLISP Development Release v.10.6.3

Postby ralph.ronnquist » Fri Jul 17, 2015 11:39 pm

I'd be happy to learn (more) about git, and fwiw in full support for this.

And I can set you up with a remote armv7 build environment if you like.
Currently with Ubuntu 12.04 but that can be flexible.

Then there's also the Android variant(s) to hopefully be included as mainstream.
ralph.ronnquist
 
Posts: 216
Joined: Mon Jun 02, 2014 1:40 am
Location: Melbourne, Australia

Re: newLISP Development Release v.10.6.3

Postby Lutz » Sat Jul 18, 2015 5:37 pm

No problem with using Git for configure-alt development. I can take new versions of configure-alt from there and can help testing on OSX, Windows 7, Ubuntu Linux and FreeBSD.

On the main newLISP code base I prefer development the way it has been done. Of course there is no problem do have a Git repository for all newLISP stable and development releases. There is one, Kosh maintains here: https://github.com/kosh04 it could be useful to see the history of code portions when fixing bugs.
Lutz
 
Posts: 5279
Joined: Thu Sep 26, 2002 4:45 pm
Location: Pasadena, California

Re: newLISP Development Release v.10.6.3

Postby TedWalther » Sat Jul 18, 2015 9:48 pm

Lutz, I was requesting that you push your changes up to kosh04 git repository similar to how you do for the inprogress branch; this way we don't just see changes between releases, but get a better sense of what changes go into a particular feature or bugfix. Then we get the benefit of the issue tracker on github also.
Cavemen in bearskins invaded the ivory towers of Artificial Intelligence. Nine months later, they left with a baby named newLISP. The women of the ivory towers wept and wailed. "Abomination!" they cried.
TedWalther
 
Posts: 605
Joined: Mon Feb 05, 2007 1:04 am
Location: Abbotsford, BC

Re: newLISP Development Release v.10.6.3

Postby TedWalther » Sat Jul 18, 2015 9:52 pm

Lutz, another reason for suggesting git for main body of newlisp development is this: to make it easier for more people to contribute, and to make it easier for you to manage a greater number of contributors. I've been wondering why languages like ruby on rails, or clojure, are more widely used than newlisp. Greater mass of contributors and use cases means more resources all around for everyone.
Cavemen in bearskins invaded the ivory towers of Artificial Intelligence. Nine months later, they left with a baby named newLISP. The women of the ivory towers wept and wailed. "Abomination!" they cried.
TedWalther
 
Posts: 605
Joined: Mon Feb 05, 2007 1:04 am
Location: Abbotsford, BC

Re: newLISP Development Release v.10.6.3

Postby Lutz » Sat Jul 18, 2015 11:29 pm

As everybody knows, I keep a tight control about what new features enter the newLISP language. If people need more use-cases, they should write modules and import libraries when necessary. For the main newLISP executable itself, I don’t want more contributors.

Having worked with most of the software version control systems like RCS, CVS, SVN besides Git and in developer teams since the late eighties in small and big companies, I am well aware what these systems can do and cannot do. For my style as mostly the sole developer they are not useful. Pushing every change to a repository is just one more thing to do, I don’t need and want.

Again, if anybody wants to capture change over versions in a public Git depository that is fine, but I will not change my style of development.

For more use cases write modules, import libraries! Publish them on the Git repository, documented! and I can put them in the index at http://www.newlisp.org/modules/
Lutz
 
Posts: 5279
Joined: Thu Sep 26, 2002 4:45 pm
Location: Pasadena, California

Next

Return to newLISP newS

Who is online

Users browsing this forum: No registered users and 1 guest

cron